[Support] binhex - DelugeVPN


Recommended Posts

does anyone know if there is a file I can copy from my delugeVPN folder that has my list of queued torrents? I think im stuck in a spot where I just have to start over on my dockers.

 

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

post a screen shot of your docker container config.

Link to comment

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

Firstly, don't panic, as long as you have configured the volume mappings correctly AND set deluge to write to these areas (i.e. /config or /data) then you wont loose anything should you need to delete the entire shooting match.

 

What mr-hexen is suggesting above is sound advice, you do NOT need to get access to the deluge webui to do the above, this will reset you back to no docker containers or images, you can then use the "user defined templates" dropdown when creating the containers again to pre-populate the config, so you should be back to a running system in around 30 mins to an hour.

 

Once you have got a new docker.img file created and re-pulled down delugevpn then run it and see what happens, if its still shagged then post back here with as much detail as possible, new supervisord.log, screnshot of the delugevpn config (with advanced switched on), syslog too.

Link to comment

does anyone know if there is a file I can copy from my delugeVPN folder that has my list of queued torrents? I think im stuck in a spot where I just have to start over on my dockers.

 

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

post a screen shot of your docker container config.

 

Thanks for the help. Here's the setup

delugevpn.jpg.38353d2aa42428b2023c1ec0ce57b9dd.jpg

Link to comment

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

Firstly, don't panic, as long as you have configured the volume mappings correctly AND set deluge to write to these areas (i.e. /config or /data) then you wont loose anything should you need to delete the entire shooting match.

 

What mr-hexen is suggesting above is sound advice, you do NOT need to get access to the deluge webui to do the above, this will reset you back to no docker containers or images, you can then use the "user defined templates" dropdown when creating the containers again to pre-populate the config, so you should be back to a running system in around 30 mins to an hour.

 

Once you have got a new docker.img file created and re-pulled down delugevpn then run it and see what happens, if its still shagged then post back here with as much detail as possible, new supervisord.log, screnshot of the delugevpn config (with advanced switched on), syslog too.

 

Thanks for the reply. I'm not overly concerned about having to reinstall. Its just if I can avoid having to re add the list of files I have queued if at all possible. At this stage I'm thinking a fresh install to stop this error is prob the way to go. I'm not sure if that earlier config change to try help improve speeds might be causing an error now?

Link to comment

does anyone know if there is a file I can copy from my delugeVPN folder that has my list of queued torrents? I think im stuck in a spot where I just have to start over on my dockers.

 

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

post a screen shot of your docker container config.

 

Thanks for the help. Here's the setup

 

Add /24 to the end of the vip address in lan_network.

Link to comment

does anyone know if there is a file I can copy from my delugeVPN folder that has my list of queued torrents? I think im stuck in a spot where I just have to start over on my dockers.

 

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

post a screen shot of your docker container config.

 

Thanks for the help. Here's the setup

 

Add /24 to the end of the vip address in lan_network.

 

Nope still same result I'm afraid. Exactly the same as my earlier logs.

Link to comment

 

Thanks for the help. Here's the setup

 

I use port 1194 (not 1196) and us-east.privateinternetaccess.com for my delugevpn setup.  I also don't see VPN_Protocol in your setup screenshot.  Mine is set for UDP.  Maybe these things are your issue?

 

If you look at earlier posts most of these are from an earlier post in relation to speed issues. Plus the PIA server isnt the issue as I am in ireland. The logs show no mention of issues with the VPN but just at a guess seems to be an issue with Read and Write privileges? again this is at a guess from looking at the logs I have already posted.

 

Just in case this is the issue would someone mind sending me the default openvpn.ovpn file in /config/openvpn? I changed mine and when it was working earlier I deleted my back up of the original. Thanks

Link to comment

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

So I've tried:

1. deleting the container and reinstalling

2. deleting the container & image and installing

3. deleting the docker.img and reinstalling the container

 

and even:

4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory

 

and still cannot open the webui!!! What is going on???

 

Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

Link to comment

I am having issues loading the webui. The docker description states:

 

"IMPORTANT - To allow access to the Deluge webui, Privoxy and Deluge deamon you need to specify you LAN network, using CIDR notation for the mask, a subnet mask of 255.255.255.0 would equate to CIDR /24, 255.255.0.0 would equate to CIDR /16."

 

Where do I specify it? The docker created two folders, config and data. Inside the config folder, an openvpn folder, which I added my AirVPN ovpn file, and also contains the supervisord log file. There is no config file.

 

----------

 

This is the command message from the docker:

 

Command:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="DelugeVPN" --net="bridge" --privileged="true" -e VPN_ENABLED="yes" -e VPN_USER="vpn username" -e VPN_PASS="vpn password" -e VPN_REMOTE="nl.privateinternetaccess.com" -e VPN_PORT="1194" -e VPN_PROTOCOL="udp" -e VPN_PROV="pia|airvpn|custom" -e ENABLE_PRIVOXY="no" -e LAN_NETWORK="192.168.1.0/24" -e DEBUG="false" -e TZ="America/Los_Angeles" -p 8112:8112/tcp -p 58846:58846/tcp -p 8118:8118/tcp -v "/mnt/cache/appdata/DelugeVPN/config/":"/config":rw -v "/mnt/cache/appdata/DelugeVPN/data/":"/data":rw binhex/arch-delugevpn

580a323fa196b22af9405e01c98abad5b43f8a1350d9fba47aeee44807ae9901

 

The command finished successfully!

 

----------

 

The LAN_NETWORK is my old local IP. Not sure if that's the issue, and I don't know how to change it in the docker. All my other docker apps work perfectly fine.

 

----------

 

Log file attached.

 

-Austin

supervisord.txt

Link to comment

does anyone know if there is a file I can copy from my delugeVPN folder that has my list of queued torrents? I think im stuck in a spot where I just have to start over on my dockers.

 

I believe the files are located in the config folder, not the docker.img.

 

Test it. Stop all dockers and the docker service.

 

Rename docker.img to docker.bak.

 

Restart your docker service and try the deluge docker again.

 

Problem i have is i cant get the docker to work at all. It says its running but i cant connect to the webui. I made a few earlier posts. No one seems to have any idea about it.

 

post a screen shot of your docker container config.

 

Thanks for the help. Here's the setup

 

Add /24 to the end of the vip address in lan_network.

 

You also have your network incorrectly defined, you now have it as 192.168.1.20/24 it shouldn't be an IP in your network, instead it should be for the network, so you should use a 0 not 20 so it should look like this:-

 

192.168.1.0/24

 

Link to comment

 

Thanks for the help. Here's the setup

 

I use port 1194 (not 1196) and us-east.privateinternetaccess.com for my delugevpn setup.  I also don't see VPN_Protocol in your setup screenshot.  Mine is set for UDP.  Maybe these things are your issue?

 

FYI gateway. port and protocol are all actually optional, if not specified then the script will grab these values from the ovpn file. If they are specified then they are written to the ovpn file.

 

Link to comment

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

So I've tried:

1. deleting the container and reinstalling

2. deleting the container & image and installing

3. deleting the docker.img and reinstalling the container

 

and even:

4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory

 

and still cannot open the webui!!! What is going on???

 

Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

 

Not without a supervisord.log file :-)

Link to comment

I am having issues loading the webui. The docker description states:

 

"IMPORTANT - To allow access to the Deluge webui, Privoxy and Deluge deamon you need to specify you LAN network, using CIDR notation for the mask, a subnet mask of 255.255.255.0 would equate to CIDR /24, 255.255.0.0 would equate to CIDR /16."

 

Where do I specify it? The docker created two folders, config and data. Inside the config folder, an openvpn folder, which I added my AirVPN ovpn file, and also contains the supervisord log file. There is no config file.

 

----------

 

This is the command message from the docker:

 

Command:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="DelugeVPN" --net="bridge" --privileged="true" -e VPN_ENABLED="yes" -e VPN_USER="vpn username" -e VPN_PASS="vpn password" -e VPN_REMOTE="nl.privateinternetaccess.com" -e VPN_PORT="1194" -e VPN_PROTOCOL="udp" -e VPN_PROV="pia|airvpn|custom" -e ENABLE_PRIVOXY="no" -e LAN_NETWORK="192.168.1.0/24" -e DEBUG="false" -e TZ="America/Los_Angeles" -p 8112:8112/tcp -p 58846:58846/tcp -p 8118:8118/tcp -v "/mnt/cache/appdata/DelugeVPN/config/":"/config":rw -v "/mnt/cache/appdata/DelugeVPN/data/":"/data":rw binhex/arch-delugevpn

580a323fa196b22af9405e01c98abad5b43f8a1350d9fba47aeee44807ae9901

 

The command finished successfully!

 

----------

 

The LAN_NETWORK is my old local IP. Not sure if that's the issue, and I don't know how to change it in the docker. All my other docker apps work perfectly fine.

 

----------

 

Log file attached.

 

-Austin

 

Edit the delugevpn container and click on the advanced settings button to right, you will then see a list of env vars,  simply modify the value for LAN_NETWORK and click save.

Link to comment

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

So I've tried:

1. deleting the container and reinstalling

2. deleting the container & image and installing

3. deleting the docker.img and reinstalling the container

 

and even:

4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory

 

and still cannot open the webui!!! What is going on???

 

Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

 

Not without a supervisord.log file :-)

 2016-02-11 00:05:53,504 CRIT Set uid to user 0
2016-02-11 00:05:53,514 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2016-02-11 00:05:53,583 INFO supervisord started with pid 1
2016-02-11 00:05:54,586 INFO spawned: 'privoxy' with pid 7
2016-02-11 00:05:54,590 INFO spawned: 'start' with pid 8
2016-02-11 00:05:54,598 INFO spawned: 'webui' with pid 9
2016-02-11 00:05:54,608 INFO spawned: 'deluge' with pid 10
2016-02-11 00:05:54,626 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-02-11 00:05:54,626 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-02-11 00:05:54,627 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-02-11 00:05:54,627 DEBG 'privoxy' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-02-11 00:05:54,640 DEBG 'deluge' stdout output:
[info] VPN enabled, configuring Deluge...

2016-02-11 00:05:54,640 DEBG 'deluge' stdout output:
[info] checking VPN tunnel local ip is valid...

2016-02-11 00:05:55,030 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2016-02-11 00:05:55,100 DEBG 'start' stdout output:
[info] VPN provider defined as pia
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2016-02-11 00:05:55,193 DEBG 'start' stdout output:
[info] Env vars not defined for remote host, port and protocol, will parse existing entries from ovpn file...

2016-02-11 00:05:55,272 DEBG 'start' stdout output:
[info] VPN provider remote gateway defined as nl.privateinternetaccess.com
[info] VPN provider remote port defined as 1194
[info] VPN provider remote protocol defined as udp

2016-02-11 00:05:55,289 DEBG 'start' stdout output:
[info] VPN provider username defined as ########

2016-02-11 00:05:55,319 DEBG 'start' stdout output:
[info] VPN provider password defined as ########

2016-02-11 00:05:55,460 DEBG 'start' stdout output:
[info] Default route for container is 172.17.42.1

2016-02-11 00:05:55,478 DEBG 'start' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2016-02-11 00:05:55,479 DEBG 'start' stderr output:
RTNETLINK answers: Invalid argument

2016-02-11 00:05:55,479 DEBG 'start' stdout output:
[info] ip route defined as follows...
--------------------

2016-02-11 00:05:55,479 DEBG 'start' stdout output:
default via 172.17.42.1 dev eth0

2016-02-11 00:05:55,480 DEBG 'start' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.8
--------------------

2016-02-11 00:05:55,562 DEBG 'start' stdout output:
[info] iptable_mangle module not supported, attempting to load...

2016-02-11 00:05:55,581 DEBG 'start' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.1.17-unRAID

2016-02-11 00:05:55,582 DEBG 'start' stdout output:
[warn] iptable_mangle module not supported, you will not be able to connect to Deluge webui or Privoxy outside of your LAN

2016-02-11 00:05:55,732 DEBG 'start' stdout output:
[info] iptables defined as follows...
--------------------

2016-02-11 00:05:55,732 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-02-11 00:05:55,733 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-02-11 00:05:55,735 DEBG 'start' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2016-02-11 00:05:55,737 DEBG 'start' stdout output:
--------------------
[info] nameservers

2016-02-11 00:05:55,738 DEBG 'start' stdout output:
nameserver 8.8.8.8
nameserver 8.8.4.4

2016-02-11 00:05:55,739 DEBG 'start' stdout output:
--------------------
[info] Starting OpenVPN...

2016-02-11 00:05:55,812 DEBG 'start' stdout output:
Thu Feb 11 00:05:55 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015

2016-02-11 00:05:55,812 DEBG 'start' stdout output:
Thu Feb 11 00:05:55 2016 library versions: OpenSSL 1.0.2f 28 Jan 2016, LZO 2.09

2016-02-11 00:05:55,812 DEBG 'start' stdout output:
Thu Feb 11 00:05:55 2016 WARNING: file 'credentials.conf' is group or others accessible

2016-02-11 00:05:55,848 DEBG 'start' stdout output:
Thu Feb 11 00:05:55 2016 UDPv4 link local: [undef]

2016-02-11 00:05:55,848 DEBG 'start' stdout output:
Thu Feb 11 00:05:55 2016 UDPv4 link remote: [AF_INET]109.201.152.245:1194

2016-02-11 00:05:55,991 DEBG 'start' stdout output:
Thu Feb 11 00:05:55 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2016-02-11 00:05:56,467 DEBG 'start' stdout output:
Thu Feb 11 00:05:56 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]109.201.152.245:1194

2016-02-11 00:05:58,356 DEBG 'start' stdout output:
Thu Feb 11 00:05:58 2016 TUN/TAP device tun0 opened
Thu Feb 11 00:05:58 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Thu Feb 11 00:05:58 2016 /usr/bin/ip link set dev tun0 up mtu 1500

2016-02-11 00:05:58,359 DEBG 'start' stdout output:
Thu Feb 11 00:05:58 2016 /usr/bin/ip addr add dev tun0 local 10.198.1.6 peer 10.198.1.5

2016-02-11 00:05:58,370 DEBG 'start' stdout output:
Thu Feb 11 00:05:58 2016 Initialization Sequence Completed

2016-02-11 00:05:58,372 DEBG 'deluge' stdout output:
[info] VPN interface (tun0) ip address format correct

2016-02-11 00:05:58,388 DEBG 'privoxy' stdout output:
[info] VPN interface (tun0) ip address format correct

2016-02-11 00:05:58,389 DEBG 'deluge' stdout output:
[info] VPN interface (tun0) is UP
[info] All checks complete, starting Deluge daemon...

2016-02-11 00:05:58,394 DEBG 'deluge' stdout output:
[info] configuring Deluge listen port...

2016-02-11 00:05:58,394 DEBG 'deluge' stdout output:
[info] Configuring Deluge listen interface...

2016-02-11 00:05:58,396 DEBG 'privoxy' stdout output:
[info] VPN interface (tun0) is UP
[info] Privoxy set to disabled

2016-02-11 00:05:58,396 DEBG fd 8 closed, stopped monitoring (stderr)>
2016-02-11 00:05:58,396 DEBG fd 6 closed, stopped monitoring (stdout)>
2016-02-11 00:05:58,396 INFO exited: privoxy (exit status 0; expected)
2016-02-11 00:05:58,397 DEBG received SIGCLD indicating a child quit
2016-02-11 00:05:58,428 DEBG 'deluge' stdout output:
[info] Manually setting Deluge listen interface to 10.198.1.6

2016-02-11 00:06:05,489 DEBG 'webui' stdout output:
[info] Starting Deluge webui...

2016-02-11 00:06:08,608 DEBG 'deluge' stdout output:
[info] Deluge incoming port 41059

2016-02-11 00:06:11,573 DEBG 'deluge' stdout output:
[info] PIA incoming port 33882
[info] Deluge incoming port 41059 and PIA incoming port 33882 different, configuring Deluge...

2016-02-11 00:06:12,471 DEBG 'deluge' stdout output:
Setting random_port to False..
Configuration value successfully updated.

2016-02-11 00:06:13,351 DEBG 'deluge' stdout output:
Setting listen_ports to (33882, 33882)..
Configuration value successfully updated.

Link to comment

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

So I've tried:

1. deleting the container and reinstalling

2. deleting the container & image and installing

3. deleting the docker.img and reinstalling the container

 

and even:

4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory

 

and still cannot open the webui!!! What is going on???

 

Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

Geez that was a frustrating one to solve... But I did it!

 

You recently made some changes and told us to modify the environment variable like this:

LAN_NETWORK    192.168.1.0/24

 

My network is different, so I typed this by mistake:

LAN_NETWORK    192.168.0.1/24

 

instead of this:

LAN_NETWORK    192.168.0.0/24

 

Can't believe how hard that was to track down. Sorry for wasting your time... :/

Link to comment

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

So I've tried:

1. deleting the container and reinstalling

2. deleting the container & image and installing

3. deleting the docker.img and reinstalling the container

 

and even:

4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory

 

and still cannot open the webui!!! What is going on???

 

Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

Geez that was a frustrating one to solve... But I did it!

 

You recently made some changes and told us to modify the environment variable like this:

LAN_NETWORK    192.168.1.0/24

 

My network is different, so I typed this by mistake:

LAN_NETWORK    192.168.0.1/24

 

instead of this:

LAN_NETWORK    192.168.0.0/24

 

Can't believe how hard that was to track down. Sorry for wasting your time... :/

 

ahh good catch, thats two people caught out by that, im seriously considering "helping" the end user by removing the last octet and setting it as zero :-)

Link to comment

I just had my unRAID machine lock up on me. Couldn't telnet in. Couldn't access the GUIs of any of my dockers, etc. I was forced to hit the reset button on the machine. After the reboot, I am not able to open the Web GUIs of Delugevpn and Sabnzbdvpn. I can open the web guis of my other dockers, and they seem to be running ok... HELP!

So I've tried:

1. deleting the container and reinstalling

2. deleting the container & image and installing

3. deleting the docker.img and reinstalling the container

 

and even:

4. deleting the docker.img, deleting the docker comtainer/image and using a new config/appdata directory

 

and still cannot open the webui!!! What is going on???

 

Well, I think I figured out my hardware issues, and my system seems to be running OK now. BUT, I cannot get Delugevpn and Sabnzbdvpn working again... Webuis will not load. I can get all my other dockers working. Any ideas?

Geez that was a frustrating one to solve... But I did it!

 

You recently made some changes and told us to modify the environment variable like this:

LAN_NETWORK    192.168.1.0/24

 

My network is different, so I typed this by mistake:

LAN_NETWORK    192.168.0.1/24

 

instead of this:

LAN_NETWORK    192.168.0.0/24

 

Can't believe how hard that was to track down. Sorry for wasting your time... :/

 

ahh good catch, thats two people caught out by that, im seriously considering "helping" the end user by removing the last octet and setting it as zero :-)

 

This also fixed my issue. 192.168.1.0/24 instead of 1/24 fixed my issue. Thank you <3

Link to comment

you need to configure a settings path and a downloads path.

 

Post a screen shot of your folder mappings for the delugeVPN container.

 

Attached

 

In the Deluge docker, set the download path to /data

 

I thought it was a little ironic that I ran into the same issue as this. I cannot get any torrents to save to mapped downloads dir, it appears it is unavailable and then it just resorts to saving inside the docker file itself??? As a fallback I guess?? I can't see in the dockerfile, but I searched for hours in user shares, spun down all drives and only one running was cache drive as my app/docker/vm disk. I did quite a bit of testing trying to figure this out. So first I will upload a few logs and a pic of my setup so you guys can see where i stand and then ill go into what I found!

 

8rQBQ85gjOkuxE1LKRkQshxVh5USqN3_uA-GuSQmnHhMQsSVWnsuWWpsfAllacOBvSsVF4FtrMHx3eBanSzmrPnhZ6abXsnO4mj7c2X8RKzqB2J2mHFPZRlJ5BEcx4oKRpO1fJVx6RITryfpoukhF-DIUEJ_Nr2KzSo1x2UGY-7TBFn18GhSfk2KqTv9_hrkdlrFwfqDo2pLX5c51qZCnLE9IVS1-SYZ3wCBIR2NP6Yog9xSb-zD_InTnEC3xmwoJWlPeBPzCf7fzAWaVv-GItLQ7YZfGzHs5WAdFpkPj9n1S9dwP_TRxaVtmEd3E-4NmqtQasbgEPlDVR5VKx0qxCGoSAkRkTsfbakM7oOou5gvisbS7XswH_pYctFFo17x2WMuUgva9NvoNQDzE10_amGG11Yue3YV3ifKEmOd39YpTv3K3jkAin-tIN510qlBZNuS6n0OlhdJK6oaEEOkYNTvYvIZQe7uHe7vIg4jEb1lMpsNWbK0tDUlWG8ZLVbgCznU64Mo0d9C-KadrG_lW5Gcb0cdr20pQImB-tiUDYaj0pI8KuopE938cCBdDqY=w1292-h298-no

 

Logs TLDR: "core:187 Failed to load lt state: [Errno 2] No such file or directory:"

 

Now, this is definitely related to the config and data mappings. But it is not full on broke/not working, LOL. I tried the using just the /data and /data/ and / and /data/downloads and /data/downloads, and a lot of other combinations. After several hours and getting no where I decided to revert back to deluge without VPN. After several more hours i found that it was the exact same issue, I then realized I did not use binhex repo before, I used linuxserver's. So i loaded it up using the same mappings path as binhex and it worked right off the bat first try. I was somewhat relieved that it wasn't myself being an idiot, yet. Use same mappings and paths inside the docker I could not get it to work.

 

Now what I did find, was that I could have a path setup in configuration for a path to save .torrents, that worked without a hitch in several locations I tried. I tried settings the paths the same for torrents and data, but only the .torrent ever showed up. Then I setup the move to when completed, that worked like a charm as well, and could be used as a TEMP fix right now. But I want to get it downloading in the right dir to begin with. I also fiddled with trying to mount to user shares and then disks/cache, neither seemed to work.

 

To top it all off, I did test my VPN torrent setup, and that is working right out of the box LOL. So once I get this figured out I will be rolling. Would appreciate any help in trying to get this resolved! Thanks in advance!

deluged1.txt

deluged4.txt

Link to comment

ahh good catch, thats two people caught out by that, im seriously considering "helping" the end user by removing the last octet and setting it as zero :-)

 

Is there anyway to read the IP of the unRAID server and default it to that and let users modify it if they only know what they're doing, i.e. "advanced view"?

Link to comment

ahh good catch, thats two people caught out by that, im seriously considering "helping" the end user by removing the last octet and setting it as zero :-)

 

 

~3rd~

 

 

I changed it to 192.168.1.1/24 , should have just left it at 192.168.1.0/24, was thinking of my gateway IP lol.

 

My unRaid is 192.168.1.250, but I believe we are just specifying the subnet and 255 range we are in?

Link to comment

ahh good catch, thats two people caught out by that, im seriously considering "helping" the end user by removing the last octet and setting it as zero :-)

 

Is there anyway to read the IP of the unRAID server and default it to that and let users modify it if they only know what they're doing, i.e. "advanced view"?

i had the exact same thought when i was coding this up, unfortunately this just isnt possible, the only way is to pass it through as an env var, i COULD do some clever stuff with the env var to try and grab the hosts ip and then make assumptions on that for the network, see below:-

 

-e "DOCKER_HOST=$(ip -4 addr show docker0 | grep -Po 'inet \K[\d.]+')"

 

stolen from here http://stackoverflow.com/questions/22944631/how-to-get-the-ip-address-of-the-docker-host-from-inside-a-docker-container

 

not sure i like this approach overly though, firstly you have to know the bridge name, and secondly the ip of the host may not be the network you want to route to, unlikely but possible.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.