[Support] binhex - DelugeVPN

[jeff.lebowski]

It's been such a difficult 18 hours, I can't even recall why I had to delete my Docker image and reinstall Deluge.

 

1) I didn't sleep well last night. Maybe 45 minutes total.

2) I am just dumb enough to not understand "Volume Mappings" and how everything works together. I could NOT make AutoAdd save the watch folder. Only after I had downloaded a couple new torrents for testing did I see my Download destination was wrong (one folder extra deep), which clicked something in my brain. I fixed the watch folder and AutoAdd now works (by the way, WTF is a .egg?) and I'm slowly re-adding the torrents.

3) The path in the Docker settings DOES NOT match what the path Deluge. That's today's tip. I believe typing out mnt/user/Torrentz in the Docker settings creates a path that Deluge sees as /data. I could not figure this out. For hours.

 

About five hours ago, I would have given my kingdom for a simple setup tutorial that clearly lays out why paths are setup the way they are. 🤪

 

I've been seeding nearly nonstop since about 2004. Thousands and thousands of sessions, with gobs and gobs of data. I *almost* considered just stopping. It was that bad today.

 

Thanks for reading. 🙂

Edited April 17, 2020 by jeff.lebowski

[wgstarks]

27 minutes ago, jeff.lebowski said:

About five hours ago, I would have given my kingdom for a simple setup tutorial that clearly lays out why paths are setup the way they are. 🤪

This may be a little dated but the principles haven’t changed.

https://youtu.be/ISJczs06pD8

[jeff.lebowski]

1 hour ago, wgstarks said:

This may be a little dated but the principles haven’t changed.

https://youtu.be/ISJczs06pD8

Thanks!

 

I watched his Deluge tutorial the first time I set it up, and thought it was a simple process. Like I didn't need to watch a second time kind of simple.

[ironsights]

Hi all. First, thanks BINHEX for this awesome docker project. I got it mostly setup but I'm having issues getting downloads to actually start. I'm using radarr and it sends the torrent over just fine, my IP address shows that I'm connected to my VPN, but the downloads never start. Peers never seem to fully connect and they drop left and right. I'm not quite sure if it's the connection part or if it's a permission issue somewhere. Where can I look to start narrowing this down? I have debugging on. I'm just not sure what logs to look at and what specifically to look for. Any advice is appreciated. Thanks!

[binhex]

7 hours ago, jeff.lebowski said:

It's been such a difficult 18 hours, I can't even recall why I had to delete my Docker image and reinstall Deluge.

 

1) I didn't sleep well last night. Maybe 45 minutes total.

2) I am just dumb enough to not understand "Volume Mappings" and how everything works together. I could NOT make AutoAdd save the watch folder. Only after I had downloaded a couple new torrents for testing did I see my Download destination was wrong (one folder extra deep), which clicked something in my brain. I fixed the watch folder and AutoAdd now works (by the way, WTF is a .egg?) and I'm slowly re-adding the torrents.

3) The path in the Docker settings DOES NOT match what the path Deluge. That's today's tip. I believe typing out mnt/user/Torrentz in the Docker settings creates a path that Deluge sees as /data. I could not figure this out. For hours.

 

About five hours ago, I would have given my kingdom for a simple setup tutorial that clearly lays out why paths are setup the way they are. 🤪

 

I've been seeding nearly nonstop since about 2004. Thousands and thousands of sessions, with gobs and gobs of data. I *almost* considered just stopping. It was that bad today.

 

Thanks for reading. 🙂

my stab at explaining some of the basics:-

https://github.com/binhex/documentation/blob/master/docker/faq/general.md

[strike]

9 hours ago, ironsights said:

Hi all. First, thanks BINHEX for this awesome docker project. I got it mostly setup but I'm having issues getting downloads to actually start. I'm using radarr and it sends the torrent over just fine, my IP address shows that I'm connected to my VPN, but the downloads never start. Peers never seem to fully connect and they drop left and right. I'm not quite sure if it's the connection part or if it's a permission issue somewhere. Where can I look to start narrowing this down? I have debugging on. I'm just not sure what logs to look at and what specifically to look for. Any advice is appreciated. Thanks!

Please follow this procedure: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

In addition to that also post your docker run command or a screenshot of the container settings.

[pnbrooks]

Hi all, 

 

So, I've just gone through the steps provided by Spaceinvader One to configure Deluge VPN on Unraid. Unfortunately, when I click on "open Web UI" I get a "this site cannot be reached" error. I've double-checked that I followed the instructions properly, but I'm still not having any luck. I've also done some google searches and haven't found anything that looks to be germane to my particular issue (but, I'm new to all this, so maybe I'm just ignorant of the ways in which other threads are relevant; apologies if that's the case). Any help y'all could provide would be very much appreciated. I've attached my logs from Deluge VPN here. Thanks in advance for your help! 

Deluge Log 4172020.txt

[wgstarks]

20 minutes ago, pnbrooks said:

Hi all, 

 

So, I've just gone through the steps provided by Spaceinvader One to configure Deluge VPN on Unraid. Unfortunately, when I click on "open Web UI" I get a "this site cannot be reached" error. I've double-checked that I followed the instructions properly, but I'm still not having any luck. I've also done some google searches and haven't found anything that looks to be germane to my particular issue (but, I'm new to all this, so maybe I'm just ignorant of the ways in which other threads are relevant; apologies if that's the case). Any help y'all could provide would be very much appreciated. I've attached my logs from Deluge VPN here. Thanks in advance for your help! 

Deluge Log 4172020.txt 15.81 kB · 3 downloads

The PIA server you are connecting to (Perth) does not support port forwarding. There is a list of servers that do about halfway through the log you posted. You should try one of them.

[ironsights]

 

11 hours ago, ironsights said:

Hi all. First, thanks BINHEX for this awesome docker project. I got it mostly setup but I'm having issues getting downloads to actually start. I'm using radarr and it sends the torrent over just fine, my IP address shows that I'm connected to my VPN, but the downloads never start. Peers never seem to fully connect and they drop left and right. I'm not quite sure if it's the connection part or if it's a permission issue somewhere. Where can I look to start narrowing this down? I have debugging on. I'm just not sure what logs to look at and what specifically to look for. Any advice is appreciated. Thanks!

Ok so I put both the supervisord.log and my docker compose file in these pastebin links. Let me know if that helps.

Edited April 17, 2020 by ironsights
clarification of problem

[pnbrooks]

13 minutes ago, wgstarks said:

The PIA server you are connecting to (Perth) does not support port forwarding. There is a list of servers that do about halfway through the log you posted. You should try one of them.

Worked like a charm. Thanks so much for the quick and helpful reply!

[Cpt. Chaz]

$2020-04-17 14:06:08,571 DEBG 'start-script' stdout output:
[warn] PIA endpoint 'au-perth.privateinternetaccess.com' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow
[info] Please consider switching to one of the endpoints shown below

$2020-04-17 14:06:08,571 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com

$2020-04-17 14:06:08,572 DEBG 'start-script' stdout output:
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com

@pnbrooks although i think the canadian endpoints have stopped working.

Edited April 17, 2020 by Cpt. Chaz
typo

[Cpt. Chaz]

ah, looks like you got it!

[Esormit88]

I've been through what seems like every solution on here. I'm very new to unRaid and have a mild knowledge of networking, so please ELI5 if you can. I cannot get the WebUI to load with VPN_ENABLED. I'm using PIA with the proper credentials. I've copied over the correct cert files and tried multiple region .ovpn files, including confirmed port forwarding locations. Logs show nothing alarming, it says WebUI started, but when I try to load the WebUI, it just never connects to it. I'm on br0 mode, locked the IP, but have tried different IP configurations, including Bridge. I've deleted and started over from scratch. I've deleted web.conf and had it rebuild. Nothing. "This site cannot be reached." WebUI loads fine with the VPN off. Can anyone please help?

2020-04-17 15:09:06,098 DEBG 'start-script' stdout output:
[info] OpenVPN started
Fri Apr 17 15:09:06 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-04-17 15:09:06,099 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:06 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.155:1198
Fri Apr 17 15:09:06 2020 UDP link local: (not bound)

2020-04-17 15:09:06,100 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:06 2020 UDP link remote: [AF_INET]199.229.249.155:1198

2020-04-17 15:09:06,388 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:06 2020 [f49e79fd4f438f94880236dbe4d0a5e4] Peer Connection Initiated with [AF_INET]199.229.249.155:1198

2020-04-17 15:09:07,586 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:07 2020 TUN/TAP device tun0 opened
Fri Apr 17 15:09:07 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-04-17 15:09:07,587 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:07 2020 /usr/bin/ip addr add dev tun0 local 10.44.10.6 peer 10.44.10.5

2020-04-17 15:09:07,588 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:07 2020 /root/openvpnup.sh tun0 1500 1558 10.44.10.6 10.44.10.5 init

2020-04-17 15:09:07,590 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2020-04-17 15:09:07,597 DEBG 'start-script' stdout output:
Fri Apr 17 15:09:07 2020 Initialization Sequence Completed

2020-04-17 15:09:07,701 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.44.10.6'

2020-04-17 15:09:07,702 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-montreal.privateinternetaccess.com' is port forward enabled...

2020-04-17 15:09:07,705 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2020-04-17 15:09:08,309 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2020-04-17 15:09:08,366 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-04-17 15:09:08,367 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-04-17 15:09:08,371 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=c17ecb588136bdfca3053ae66d423197b80c518f5c260a69249a2cdefceeaed5...

2020-04-17 15:09:08,863 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=c17ecb588136bdfca3053ae66d423197b80c518f5c260a69249a2cdefceeaed5, response code 200

2020-04-17 15:09:08,890 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 42792

2020-04-17 15:09:08,891 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-04-17 15:09:08,960 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.164.228'

2020-04-17 15:09:08,961 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-04-17 15:09:09,463 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 199.229.249.155

2020-04-17 15:09:09,726 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-04-17 15:09:09,732 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.44.10.6 different, marking for reconfigure

2020-04-17 15:09:09,736 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2020-04-17 15:09:09,741 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2020-04-17 15:09:09,741 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 42792 different, marking for reconfigure

2020-04-17 15:09:09,741 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2020-04-17 15:09:10,000 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.1.10.6'
[info] Deluge key 'listen_interface' will have a new value '10.44.10.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-04-17 15:09:10,135 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2020-04-17 15:09:10,258 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'bef87a7dd78145fe9fc4d12332d989d3'
[info] Deluge key 'default_daemon' will have a new value 'bef87a7dd78145fe9fc4d12332d989d3'
[info] Writing changes to Deluge config file '/config/web.conf'...

2020-04-17 15:09:10,482 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2020-04-17 15:09:10,693 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2020-04-17 15:09:12,410 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2020-04-17 15:09:14,199 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (42792, 42792)
Configuration value successfully updated.

2020-04-17 15:09:15,758 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2020-04-17 15:09:15,758 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

2020-04-17 15:09:15,758 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42792
[debug] Deluge incoming port is 42792
[debug] VPN IP is 10.44.10.6
[debug] Deluge IP is 10.44.10.6

2020-04-17 15:09:45,762 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-04-17 15:09:45,768 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-04-17 15:09:45,778 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42792
[debug] Deluge incoming port is 42792
[debug] VPN IP is 10.44.10.6
[debug] Deluge IP is 10.44.10.6

2020-04-17 15:10:15,782 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-04-17 15:10:15,788 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-04-17 15:10:15,797 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42792
[debug] Deluge incoming port is 42792
[debug] VPN IP is 10.44.10.6
[debug] Deluge IP is 10.44.10.6

2020-04-17 15:10:45,802 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-04-17 15:10:45,808 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-04-17 15:10:45,817 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42792
[debug] Deluge incoming port is 42792
[debug] VPN IP is 10.44.10.6
[debug] Deluge IP is 10.44.10.6

2020-04-17 15:11:15,822 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-04-17 15:11:15,828 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-04-17 15:11:15,837 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42792
[debug] Deluge incoming port is 42792
[debug] VPN IP is 10.44.10.6
[debug] Deluge IP is 10.44.10.6

2020-04-17 15:11:45,842 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-04-17 15:11:45,848 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-04-17 15:11:45,857 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42792
[debug] Deluge incoming port is 42792
[debug] VPN IP is 10.44.10.6
[debug] Deluge IP is 10.44.10.6

Edited April 17, 2020 by [email protected]

[strike]

2 hours ago, ironsights said:

 

Ok so I put both the supervisord.log and my docker compose file in these pastebin links. Let me know if that helps.

Ok, so a few things here.
1. Nordvpn does not support port forwarding so even if you were able to get it to work your speed will be slow at best. It wil also only work on public trackers since you won't be able to seed. So do yourself a favor and switch vpn provider
2. VPN_PROV is defined as nordvpn, AFAIK there is only three valid options PIA, Airvpn or custom. If you don't have PIA or airvpn it should be custom.
3. Are your volume mappings corrrect? What path do you have under downloads in the deluge settings? Even if it's correct it won't work well with the radarr container you have. These two containers needs to share the same volume mapping for downloads, or else radarr won't be able to see the downloads when deluge is finished with them. So you need to change the container side of the mapping for one of them so they match.

[ironsights]

29 minutes ago, strike said:

Ok, so a few things here.
1. Nordvpn does not support port forwarding so even if you were able to get it to work your speed will be slow at best. It wil also only work on public trackers since you won't be able to seed. So do yourself a favor and switch vpn provider
2. VPN_PROV is defined as nordvpn, AFAIK there is only three valid options PIA, Airvpn or custom. If you don't have PIA or airvpn it should be custom.
3. Are your volume mappings corrrect? What path do you have under downloads in the deluge settings? Even if it's correct it won't work well with the radarr container you have. These two containers needs to share the same volume mapping for downloads, or else radarr won't be able to see the downloads when deluge is finished with them. So you need to change the container side of the mapping for one of them so they match.

1. I didn't know they didn't support port forwarding, but I've already got their membership for another year or so, so I'm stuck with them for now. But I was using NordVPN with haugene / docker-transmission-openvpn and it worked pretty good.

2 and 3. I fixed both of those discrepancies but with the same result. Every torrent is showing the tracker status as timed out and the downloads stay at 0%. Here's my updated docker-compose file.

[strike]

39 minutes ago, [email protected] said:

I'm on br0 mode, locked the IP

br0 is not supported in this container change to bridge. Or you might be able to get access if you use the desktop/thin client insted of the webui on br0. Check the faq on who to set it up if you want to try that. Is your LAN_Network defined correctly? What have you defined and what Ip are you connecting to?

[strike]

8 minutes ago, ironsights said:

1. I didn't know they didn't support port forwarding, but I've already got their membership for another year or so, so I'm stuck with them for now. But I was using NordVPN with haugene / docker-transmission-openvpn and it worked pretty good.

2 and 3. I fixed both of those discrepancies but with the same result. Every torrent is showing the tracker status as timed out and the downloads stay at 0%. Here's my updated docker-compose file.

Disable strcict port forwarding too and try again. Your volume mapping looks better, but what path do you have under downloads in deluge?

Edited April 17, 2020 by strike

[ironsights]

5 minutes ago, strike said:

Disable strcict port forwarding too and try again. Your volume mapping looks better, but what path do you have under downloads in deluge?

Ok did that. Same thing so far. It's weird because it'll look like they start downloading go to like 0.15% then drop off and go back to 0%.

[ironsights]

Here's another screenshot of deluge if it helps.

[strike]

5 minutes ago, ironsights said:

Ok did that. Same thing so far. It's weird because it'll look like they start downloading go to like 0.15% then drop off and go back to 0%.

Yeah, your settings are still not correct, you need to understand how volume mappings work.  The download path to should be /downloads

I also strongly recommend setting an incomplete and a complete folder. So the download path then should be /downloads/incomplete also check move completed to and set it to /downloads/complete

[strike]

Looks like you're using labels too so make sure the paths are correct under there too. If you set incomplete/complete folders and lables make sure to change the settings radarr accordingly 

Edited April 17, 2020 by strike

[Esormit88]

35 minutes ago, strike said:

br0 is not supported in this container change to bridge. Or you might be able to get access if you use the desktop/thin client insted of the webui on br0. Check the faq on who to set it up if you want to try that. Is your LAN_Network defined correctly? What have you defined and what Ip are you connecting to?

As stated, I've tried Bridge, but it doesn't change anything. LAN_Network has been tried in many formats. including 192.168.1.0/24, blank, and matching IP i set to as br0. I use br0 on everything, including DelugeVPN at the moment, everything works until I try enabling the VPN, but like I said, even on Bridge, WebUI will not load.

[ironsights]

  

25 minutes ago, strike said:

Yeah, your settings are still not correct, you need to understand how volume mappings work.  The download path to should be /downloads

I also strongly recommend setting an incomplete and a complete folder. So the download path then should be /downloads/incomplete also check move completed to and set it to /downloads/complete

 

 

Ok. Thank you so much for clearing that up. I could not grasp the concept of volume mappings for the life of me. I have it setup like you suggested. I don't really know how the labels work though tbh. Does that just make another directory in the downloads directory?

 

Also downloads are still saying tracker timed out.

Edited April 17, 2020 by ironsights

[strike]

2 minutes ago, [email protected] said:

As stated, I've tried Bridge, but it doesn't change anything. LAN_Network has been tried in many formats. including 192.168.1.0/24, blank, and matching IP i set to as br0. I use br0 on everything, including DelugeVPN at the moment, everything works until I try enabling the VPN, but like I said, even on Bridge, WebUI will not load.

Since you say lan_network has been tried in many formats it says to me that you don't really know what to put there. And setting it to blank and to match the IP set on br0 confirms that. There is really only one value that works for your network, no point in trying multiple.  So in order to know whats correct I really want to know your routers IP or what Ip your're connecting to when you try to reach the webui. And as I said there's no point in trying to reach the webui on br0, if you want to use br0 try the desktop/thin client like I mentioned.

[strike]

4 minutes ago, ironsights said:

I could not grasp the concept of volume mappings for the life of me.

Lol we've all been there 😆

 

6 minutes ago, ironsights said:

I don't really know how the labels work though tbh. Does that just make another directory in the downloads directory?

Yeah, it basically tells deluge to put the finished downloads in the correct folder. If you're using radarr then you're probably using sonarr or something else for tv shows too, and if you have no labels deluge with put everything in one folder, so it becomes a mess for radarr/sonarr trying to figure out what is a movie and what is a tv show. As a result the logs will just fill up with errors. So labels is a good thing, but you need to set the paths correctly there too or else it won't work as intended.