Kantraz

Members
  • Posts

    16
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Kantraz's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Suddenly getting this error: NOTE: unable to redirect default gateway -- VPN gateway parameter (--route-gateway or --ifconfig) is missing Can't access the webui or flood ?
  2. Hi, is it possible to update Sabnzbd to version 1.2?
  3. Alright, I think it work now after changing to this server
  4. I meant, which of their servers you connect to I do have a router, but I have forwarded the incoming connection port
  5. I can't get it to be green What vpn gateway do you connect to?
  6. I am having no issues with seeding with VPN enabled. What VPN provider are you using? I'm using PIA
  7. Hey guys, am I the only one that can't get deluge to seed when using this? Download works at maximum speed, but I can't get it to seed, which is no problem when running just deluge Anyone got a fix for this issue?
  8. yeah i too have been investigating this further for you, i have tested this on my openelec appliance and i can see the same issue, so thats good, took me a while but i have a fix for this by adding in an additional route, im still investigating at this point as i want to get this as tight as possible, i cannot allow any ip leakage so this will be nailed. Sounds great! Hopefully my temporary fix won't result in any leaks
  9. unraid makes things easier as it has a nice webui which does all the hard work of constructing the docker run command for you, having said that, the run command you posted above looks fine, can you post your supervisord.log file please, minus any sensitive info, also the contents of your ovpn config file. Aaah, I've attached the log file and here is the contents of the ovpn file: ok i see nothing wrong with this at all, the log is reporting success, the tunnel is established, deluge looks to start correctly and the incoming port is set, are you sure you cant connect to deluge webui on http://<your hosts ip>:8112 I can connect to it on my server using hostname:8112 but as soon as i try from another client i got no success ok so the other client is on your lan yes?, and your attempting to connect to the webui NOT the daemon right?, if it is the webui then yes you should be able to connect to this from any machine on the lan, do you have any firewall rules defined on your host?. edit - are you attempting to connect using hostname or ip address?, if hostname then make sure you can resolve the name on the clients your attempting to connect with, maybe try ip address of your host instead of name. Yes, trying to connect to the webui from other machines on my lan. Tried used both hostname and IP = no luck I'm not certain whether I have firewall rules defined though, how do I check? type this on your host:- iptables -L This will list out all iptable entries. root@ubuntu:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (1 references) target prot opt source destination ACCEPT tcp -- anywhere 172.17.0.9 tcp dpt:8112 ACCEPT tcp -- anywhere 172.17.0.9 tcp dpt:8118 ok so nothing blocking there, its very odd, have you tried another browser on your client machines?, or tried forcing a clear down of caching, what error are you seeing on the client machines? Tried both Getting this error in chrome: This webpage is not available ERR_CONNECTION_REFUSED Edit: Okay, I finally got it working, though not quite sure on how as I don't understand iptables If I run "iptables -t nat -A POSTROUTING -j MASQUERADE" then it works, but now I need to figure out how to get this run at each boot
  10. unraid makes things easier as it has a nice webui which does all the hard work of constructing the docker run command for you, having said that, the run command you posted above looks fine, can you post your supervisord.log file please, minus any sensitive info, also the contents of your ovpn config file. Aaah, I've attached the log file and here is the contents of the ovpn file: ok i see nothing wrong with this at all, the log is reporting success, the tunnel is established, deluge looks to start correctly and the incoming port is set, are you sure you cant connect to deluge webui on http://<your hosts ip>:8112 I can connect to it on my server using hostname:8112 but as soon as i try from another client i got no success ok so the other client is on your lan yes?, and your attempting to connect to the webui NOT the daemon right?, if it is the webui then yes you should be able to connect to this from any machine on the lan, do you have any firewall rules defined on your host?. edit - are you attempting to connect using hostname or ip address?, if hostname then make sure you can resolve the name on the clients your attempting to connect with, maybe try ip address of your host instead of name. Yes, trying to connect to the webui from other machines on my lan. Tried used both hostname and IP = no luck I'm not certain whether I have firewall rules defined though, how do I check? type this on your host:- iptables -L This will list out all iptable entries. root@ubuntu:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (1 references) target prot opt source destination ACCEPT tcp -- anywhere 172.17.0.9 tcp dpt:8112 ACCEPT tcp -- anywhere 172.17.0.9 tcp dpt:8118
  11. unraid makes things easier as it has a nice webui which does all the hard work of constructing the docker run command for you, having said that, the run command you posted above looks fine, can you post your supervisord.log file please, minus any sensitive info, also the contents of your ovpn config file. Aaah, I've attached the log file and here is the contents of the ovpn file: ok i see nothing wrong with this at all, the log is reporting success, the tunnel is established, deluge looks to start correctly and the incoming port is set, are you sure you cant connect to deluge webui on http://<your hosts ip>:8112 I can connect to it on my server using hostname:8112 but as soon as i try from another client i got no success ok so the other client is on your lan yes?, and your attempting to connect to the webui NOT the daemon right?, if it is the webui then yes you should be able to connect to this from any machine on the lan, do you have any firewall rules defined on your host?. edit - are you attempting to connect using hostname or ip address?, if hostname then make sure you can resolve the name on the clients your attempting to connect with, maybe try ip address of your host instead of name. Yes, trying to connect to the webui from other machines on my lan. Tried used both hostname and IP = no luck I'm not certain whether I have firewall rules defined though, how do I check?
  12. unraid makes things easier as it has a nice webui which does all the hard work of constructing the docker run command for you, having said that, the run command you posted above looks fine, can you post your supervisord.log file please, minus any sensitive info, also the contents of your ovpn config file. Aaah, I've attached the log file and here is the contents of the ovpn file: ok i see nothing wrong with this at all, the log is reporting success, the tunnel is established, deluge looks to start correctly and the incoming port is set, are you sure you cant connect to deluge webui on http://<your hosts ip>:8112 I can connect to it on my server using hostname:8112 but as soon as i try from another client i got no success
  13. unraid makes things easier as it has a nice webui which does all the hard work of constructing the docker run command for you, having said that, the run command you posted above looks fine, can you post your supervisord.log file please, minus any sensitive info, also the contents of your ovpn config file. Aaah, I've attached the log file and here is the contents of the ovpn file: supervisord.txt
  14. Dang, thought it was the same to get it working on ubuntu Edit: Well now I found out it is something to do with the VPN, as when I disable the vpn and only run deluge, I can perfectly access it