Hey all, I installed DelugeVPN today, and was able to add my Wireguard credentials. I can open up the UI and add torrents, but the torrents never seem to start. I tried a few torrents, and even the official Ubuntu torrent - and nothing ever starts. 

 

Note: I am using Windscribe VPN.

 

Any idea where to look? I took at peel at the logs and nothing jumped out at me. 

 

 

 

has anyone gotten this to work with a dedicated ip assigned by the vpn provider? i have gone over the provider's doc's and the vpn.md for docker container but for some reason i have no idea why it won't use the dedicated ip, i have tried to change the  "remote" domain "ca-toronto.privacy.network 1197" for example to the ip i was assigned, still have the auth-user-pass.conf in there and it fails to connect and therefore also doesn't finish the startup for the container when the ip is used. here is the the main part of the config file if anyone has any idea how to specify how the container connects and to what ip, that would be great.

client
dev tun
proto udp
remote ca-toronto.privacy.network 1197 "Tried to change this to the ip of the dedicated ip i was assigned without success"
resolv-retry infinite
nobind
persist-key
persist-tun
cipher aes-256-cbc
auth sha256
tls-client
remote-cert-tls server

auth-user-pass
compress
verb 1
reneg-sec 0

 

5 hours ago, strike said:

How are you trying to reach the webui? If you're using the ip adress to try to reach the webui you're doing it wrong. Like it says in the faq you have to use localhost. As in http://localhost:9696 to reach prowlarr. 

Ah, okay; I see now that Q25 meant LocalHost in the url of the browser, not in a specific setting of the docker (although, I could just set the WebUI setting in the docker to be "http://localhost:[PORT:9696]/", right?)

 

However, this still doesn't seem to work? Should I be able to use "localhost:9696" from any browser url on my LAN? It currently says "Localhost refused to connect" 

 

When I change the dockers WebUI value to "http://localhost:[PORT:9696]/" and try to open it, I get the same "about:blank#blocked" error. (same for "http://[localhost]:[PORT:9696]" and "http://[localhost]:[PORT:9696]/"

 

When I change it to "http://localhost:9696" and try to open it, I get the "localhost refused to connect" error

Edited August 13, 20223 yr by Shu

17 hours ago, Nexus said:

Hey all, I installed DelugeVPN today, and was able to add my Wireguard credentials. I can open up the UI and add torrents, but the torrents never seem to start. I tried a few torrents, and even the official Ubuntu torrent - and nothing ever starts. 

 

Note: I am using Windscribe VPN.

 

Any idea where to look? I took at peel at the logs and nothing jumped out at me. 

 

 

 

Post your docker run command and a screenshot of the downloads settings in deluge.

17 hours ago, JOSEPH ENGELMANN said:

has anyone gotten this to work with a dedicated ip assigned by the vpn provider? i

What ip are you trying to connect to?

16 hours ago, Shu said:

However, this still doesn't seem to work? Should I be able to use "localhost:9696" from any browser url on my LAN? It currently says "Localhost refused to connect" 

Yes, you should be able to use it from any browser. Don't know why it's not working. Maybe post your docker run command or a screenshot of your container settings.

1 hour ago, strike said:

Post your docker run command and a screenshot of the downloads settings in deluge.

 

Here is my run command

 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Altair8800" -e HOST_CONTAINERNAME="binhex-delugevpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='REDACTED' -e 'VPN_PASS'='REDACTED' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='10.0.0.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8112]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/deluge-icon.png' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn' 
3a8b02831bacf054c7a81d195f21968bc63164fe4b6262354bd1dcb6e30cf7ed

The command finished successfully!

 

and download settings in the attached screenshot. 

 

 

 

 

10 minutes ago, Nexus said:

 

Here is my run command

 

 

and download settings in the attached screenshot. 

 

That looks good. Are you using open or private trackers? If private, maybe the deluge version you're running is blacklisted? Also search for windscribe in this thread, maybe someone has had the same issue. I certainly remember someone mentioning windscribe in this thread. 

6 minutes ago, strike said:

That looks good. Are you using open or private trackers? If private, maybe the deluge version you're running is blacklisted? Also search for windscribe in this thread, maybe someone has had the same issue. I certainly remember someone mentioning windscribe in this thread. 

Thanks - using open trackers. I tested a few from TPB (TESTING ONLY!) and they fell victim to the same issue. Downloads never starts.  I will look again for anyone w/ Windscribe issues. 

 

In the config- I did enter my windscribe credentials. Do I need do that since they are contained in the .CONF file I dropped in the /wireguard/ directory ? 
 

2 hours ago, strike said:

Yes, you should be able to use it from any browser. Don't know why it's not working. Maybe post your docker run command or a screenshot of your container settings.

Here's the docker run command. I found the same issue with other VPN containers (OpenVPN) and with trying to route other apps (Firefox) - the WebUI works when the net is bridged but doesn't work when routed through the VPN docker. 
Here is docker run for prowlarr

 

Here is docker run for binhex-delugeVPN

Edited August 13, 20223 yr by Shu

8 minutes ago, Nexus said:

In the config- I did enter my windscribe credentials. Do I need do that since they are contained in the .CONF file I dropped in the /wireguard/ directory ? 

I wouldn't know since I don't use wireguard. 

3 minutes ago, Shu said:

Here's the docker run command

I meant the ducker run command for delugevpn

1 hour ago, strike said:

I meant the ducker run command for delugevpn

Sorry about that. Added it in! Also posted here just in case

 

 

On 8/13/2022 at 7:19 AM, strike said:

How are you trying to reach the webui? If you're using the ip adress to try to reach the webui you're doing it wrong. Like it says in the faq you have to use localhost. As in http://localhost:9696 to reach prowlarr. 

Sorry but this is not correct. you only use localhost in the settings within the container that is sharing the VPN network. So in this case, Prowlarr could connect to the deluge-vpn download client app via localhost (same for Sonarr/Radarr if those are sharing the same VPN network)
But from a web browser on a separate PC on your LAN, you should not use localhost. That would cause the web browser to look for apps exposing that port on the PC itself, not the unraid server...

So from a PC web browser, you need to use the unraid server IP + the prowlarr app port (9696).

Edited August 14, 20223 yr by Jorgen
clarity

4 hours ago, Shu said:

Sorry about that. Added it in! Also posted here just in case

 

 

Your issue is that you specified the input port for Prowlarr (9696) as UDP, it needs to be TCP.

 

Edited August 14, 20223 yr by Jorgen

On 8/13/2022 at 11:17 AM, JOSEPH ENGELMANN said:

has anyone gotten this to work with a dedicated ip assigned by the vpn provider? i have gone over the provider's doc's and the vpn.md for docker container but for some reason i have no idea why it won't use the dedicated ip, i have tried to change the  "remote" domain "ca-toronto.privacy.network 1197" for example to the ip i was assigned, still have the auth-user-pass.conf in there and it fails to connect and therefore also doesn't finish the startup for the container when the ip is used. here is the the main part of the config file if anyone has any idea how to specify how the container connects and to what ip, that would be great.

 

Hmm, not much info on how the dedicated IP works, but this part from their FAQ doesn't sound great for using it with this container:

 

https://helpdesk.privateinternetaccess.com/kb/articles/do-you-offer-dedicated-ip-addresses

1 hour ago, Jorgen said:

Your issue is that you specified the input port for Prowlarr (9696) as UDP, it needs to be TCP.

 

I changed from UDP to TCP. For Key 13, do I need to put "9696" or "9696/tcp"? 

 

1 hour ago, Jorgen said:

Sorry but this is not correct. you only use localhost in the settings within the container that is sharing the VPN network. So in this case, Prowlarr could connect to the deluge-vpn download client app via localhost (same for Sonarr/Radarr if those are sharing the same VPN network)
But from a web browser on a separate PC on your LAN, you should not use localhost. That would cause the web browser to look for apps exposing that port on the PC itself, not the unraid server...

So from a PC web browser, you need to use the unraid server IP + the prowlarr app port (9696).

 

Okay, so I tried setting Prowlarr's WebUI value to a few different things but none of them worked...

"http://localhost:9696" - "localhost refused to connect"

"http://localhost:[PORT:9696]" - "about:blank#blocked"

"http://[localhost]:[PORT:9696]" - "about:blank#blocked"

 

Or when I just type in my servers IP plus the port in my browser's URL ("http://192.168.1.3:9696/"), I get a "took too long to respond" error. 

4 hours ago, Shu said:

I changed from UDP to TCP. For Key 13, do I need to put "9696" or "9696/tcp"? 

 

 

Okay, so I tried setting Prowlarr's WebUI value to a few different things but none of them worked...

"http://localhost:9696" - "localhost refused to connect"

"http://localhost:[PORT:9696]" - "about:blank#blocked"

"http://[localhost]:[PORT:9696]" - "about:blank#blocked"

 

Or when I just type in my servers IP plus the port in my browser's URL ("http://192.168.1.3:9696/"), I get a "took too long to respond" error. 

 

For key 13 (VPN_INPUT_PORTS) only the port number. So "9696, 3000" in your case

 

After that, http://192.168.1.3:9696 should work to access the Prowlarr Web UI from your PC web browser.

 

10 hours ago, Jorgen said:

 

For key 13 (VPN_INPUT_PORTS) only the port number. So "9696, 3000" in your case

 

After that, http://192.168.1.3:9696 should work to access the Prowlarr Web UI from your PC web browser.

 

That worked! Thank you so much 

21 hours ago, Jorgen said:

 

Hmm, not much info on how the dedicated IP works, but this part from their FAQ doesn't sound great for using it with this container:

 

https://helpdesk.privateinternetaccess.com/kb/articles/do-you-offer-dedicated-ip-addresses

thank you.

Version 2.1.1

Default password no longer functional. 

 

Behavior

• Upon clicking the login button with default password "deluge", entered credentials are removed and login pop-in window is reset asking for a password. No login failure notice. 
• If I try anything else other than "deluge", I get the proper login failed message "You entered an incorrect password"
• Integration with Sonarr & Radarr still functional. 

Testing so far

• I have uninstalled the app
• -rm the app data
• Reinstalled 
• No change in behavior. 
• Tried authentication in multiple browsers and machines. 

Any suggestions?

 

A bit of a general question here: I've currently got a setup with this container where I've routed other binhex containers through it as specified by Q24-27 of the VPN FAQ. One issue I've run into this setup is that if I have multiple instances of a container I want routed through it (ie. radarr), I can't because I can't use alternate port mappings. I've also started looking at the new Wireguard tunnels available directly in unraid and routing dockers through it.

How do these two methods compare to each other? Option 2 seems simpler and more flexible in being able to support multiple container instances. But is there something that I'd be loosing by going with it?

4 minutes ago, Caldorian said:

if I have multiple instances of a container I want routed through it (ie. radarr), I can't because I can't use alternate port mappings.

Since the app controls the listening IP, you should simply change the IP in radarr itself.

8 hours ago, JonathanM said:

Since the app controls the listening IP, you should simply change the IP in radarr itself.

Thanks. Definitely something I should have thought of on my own, so a good reminder that I could do that. Unfortunately I've also got other containers where I don't have that control, or that it doesn't work (ie. binhex-sabnzbd)

Honestly, at this point I'm really grasping at straws...

 

Synology's firewall, for some reason doesn't allow me to access the Web Gui (nas_ip:8112); no matter how I change the rules, or add TCP ports.

On the other side, everything works fine when I disable the firewall. *sigh*

 

Any ideas?