[Support] binhex - DelugeVPN


8746 posts in this topic Last Reply

Recommended Posts

  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

11 minutes ago, binhex said:

did you put in the external ip assigned to you from the vpn provider? (shown in the log), otherwise if using your isp's assigned ip it will show the port closed.

could have pointed that out, sorry. Yes, I did that.

Currently it's:

2021-06-10 14:15:49,273 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 20694
[debug] Deluge incoming port is 20694
[debug] VPN IP is 10.23.112.2
[debug] Deluge IP is 10.23.112.2

feel free to double check.

 

It just fixed itself (at least according to the tracker), I don't know what happened, but it seems like it takes more than half an hour to get the port forwarded... or something else happened. But checking on the website still reports as port is not forwarded.

 

I added the log file where this must have happened. 

supervisord.log

Edited by Autchirion
fixed itself
Link to post
10 minutes ago, Autchirion said:

could have pointed that out, sorry. Yes, I did that.

Currently it's:


2021-06-10 14:15:49,273 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 20694
[debug] Deluge incoming port is 20694
[debug] VPN IP is 10.23.112.2
[debug] Deluge IP is 10.23.112.2

feel free to double check.

ahh sorry my bad, looks like i echo out the internal tunnel ip address not the external ip, so for your example above 10.23.112.2 will be internal only, you need the external ip, this can be found by opening terminal for the container and running the command:-

curl ifconfig.io

this will return an ip, copy and paste this into https://www.yougetsignal.com/tools/open-ports/ with the currently assigned port (check log as it can change) and test it, i think you will find its open.

Link to post
31 minutes ago, binhex said:

ahh sorry my bad, looks like i echo out the internal tunnel ip address not the external ip, so for your example above 10.23.112.2 will be internal only, you need the external ip, this can be found by opening terminal for the container and running the command:-


curl ifconfig.io

this will return an ip, copy and paste this into https://www.yougetsignal.com/tools/open-ports/ with the currently assigned port (check log as it can change) and test it, i think you will find its open.

 

Thank you, that worked out well, so I would assume it's a tracker issue because of the randomly changing port after a reboot of the container.

 

Suggestion: Add the output of the external IP into the log.

Link to post
Just now, Autchirion said:

Thank you, that worked out well, so I would assume it's a tracker issue because of the randomly changing port after a reboot of the container.

you will get a randomly assigned ip AND a randomly assigned port on reboot, nothing can be done about this for PIA currently as both are dynamic.

 

1 minute ago, Autchirion said:

Suggestion: Add the output of the external IP into the log.

i could do but its another sensitive bit of info that i dont really want to expose in the logs.

Link to post
Just now, binhex said:

you will get a randomly assigned ip AND a randomly assigned port on reboot, nothing can be done about this for PIA currently as both are dynamic.

 

i could do but its another sensitive bit of info that i dont really want to expose in the logs.

of course, I understand this limitation of PIA, that's up to the tracker admin now... 🙂

 

Ah, that's a good thought to not put it into the log to keep it more private. Thank you for always thinking about our privacy!

Link to post
On 5/29/2021 at 8:43 PM, wgstarks said:

Scroll up to the post right above yours.

Alright, finally got around to this.

 

It fixes the WebUI, but the containers I'm routing through Binhex's container gets no connection. The Binhex container is still connected though.

 

NZBGet has the extra parameter: --net=container:binhex-delugevpn

Network type is set to "None"

Deluge has a variable called "VPN_INPUT_PORTS" with "6789" in the field.

Deluge also has a port for "6789"

 

Again, the WebUI works, Binhex's container works, but the containers routed through the Binhex's container get no connection.

Link to post

Thanks for making this docker.

 

I setup everything through CA, .opvpn file copied to correct path, but with VPN enabled, the docker will not start. It gets stuck at 

2021-06-11 17:24:36,945 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2021-06-11 17:24:36,945 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2021-06-11 17:24:36,945 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2021-06-11 17:24:36,947 DEBG 'watchdog-script' stdout output:
[info] Configuring Privoxy...

2021-06-11 17:24:36,986 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-06-11 17:24:38,055 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2021-06-11 17:24:38,060 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118


Under the docker, it says started, but webUI returns ERR_CONNECTION_TIMED_OUT.

What log do I need to provide, and how to get it? Thanks.

Link to post
On 6/10/2021 at 10:27 PM, Stubbs said:

Alright, finally got around to this.

 

It fixes the WebUI, but the containers I'm routing through Binhex's container gets no connection. The Binhex container is still connected though.

 

NZBGet has the extra parameter: --net=container:binhex-delugevpn

Network type is set to "None"

Deluge has a variable called "VPN_INPUT_PORTS" with "6789" in the field.

Deluge also has a port for "6789"

 

Again, the WebUI works, Binhex's container works, but the containers routed through the Binhex's container get no connection.

When you read the faq to get the webui working it didn't occur to you to continue reading it? See Q27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to post
8 hours ago, jiyang1018 said:

Thanks for making this docker.

 

I setup everything through CA, .opvpn file copied to correct path, but with VPN enabled, the docker will not start. It gets stuck at 




2021-06-11 17:24:36,945 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found


2021-06-11 17:24:36,945 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2021-06-11 17:24:36,945 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2021-06-11 17:24:36,947 DEBG 'watchdog-script' stdout output:
[info] Configuring Privoxy...

2021-06-11 17:24:36,986 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-06-11 17:24:38,055 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2021-06-11 17:24:38,060 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118


Under the docker, it says started, but webUI returns ERR_CONNECTION_TIMED_OUT.

What log do I need to provide, and how to get it? Thanks.

If I have to guess it's probably your LAN_NETWORK being wrong. See Q4: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md 

If you still can't get it to work do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Edited by strike
Link to post

When I originally set up sonarr/radarr/prowlarr to run through deluge vpn I did it all remotely and after doing some bits in the containers like changing to localhost it all works completely fine when I remote in to the server through openvpn. 

 

However when I try accessing locally I can't access the webgui, does anyone know why this is and how I can get it to work? Now if I want to access sonarr/radarr/prowlarr locally I have to connect through openvpn for it to work which while not a massive deal is annoying and I'd like to understand why it doesn't work with just the servers local ip and port number. (deluge vpn and all other containers not running through deluge can be accessed normally locally).

 

Fixed: For anyone else that looks at this having the same problem make sure you add the port numbers in VPN_INPUT as well as creating the port variables.

Edited by jammo
Link to post

Having some trouble getting this docker to start for me at the moment. All was working ok until my cache disk ran out of space which caused DelugeVPN to stop/shutdown. Now each time I start (even after removing /config data, and reinstalling the image) I get the errors below, and then DelugeVPN stops


/usr/local/bin/init.sh: line 488: 76 Bus error chown -R "${PUID}":"${PGID}" "/config/openvpn" &> /dev/null


/usr/local/bin/init.sh: line 525: 181 Bus error chown -R "${PUID}":"${PGID}" /etc/privoxy /home/nobody
 

Starting with VPN disabled, stops the first one showing, but it still does not start. Any help to get it going again is appreciated.

 

 

 

supervisord.log

Link to post
On 6/12/2021 at 1:48 AM, strike said:

If I have to guess it's probably your LAN_NETWORK being wrong. See Q4: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md 

If you still can't get it to work do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

My LAN_NETWORK was set correctly.

I follow the help.md page, deleted log and turned on debug. Strangely, it works without any problem. I used torguard and it shows my vpn IP in vegas correctly. 

I stopped the docker, turn degub off, and it works without any issue, showing VPN IP to torguard.

At this point, should I still provide log file or just keep it running until issue comes up again?

Link to post
7 minutes ago, jiyang1018 said:

My LAN_NETWORK was set correctly.

I follow the help.md page, deleted log and turned on debug. Strangely, it works without any problem. I used torguard and it shows my vpn IP in vegas correctly. 

I stopped the docker, turn degub off, and it works without any issue, showing VPN IP to torguard.

At this point, should I still provide log file or just keep it running until issue comes up again?

No point in posting the log if everything is working. Maybe the vpn server you connected to had issues. You won't be able to see the webui before the vpn tunnel is up. 

Link to post
On 6/12/2021 at 11:37 PM, jammo said:

When I originally set up sonarr/radarr/prowlarr to run through deluge vpn I did it all remotely and after doing some bits in the containers like changing to localhost it all works completely fine when I remote in to the server through openvpn. 

 

However when I try accessing locally I can't access the webgui, does anyone know why this is and how I can get it to work? Now if I want to access sonarr/radarr/prowlarr locally I have to connect through openvpn for it to work which while not a massive deal is annoying and I'd like to understand why it doesn't work with just the servers local ip and port number. (deluge vpn and all other containers not running through deluge can be accessed normally locally).

See Q25 and maybe 27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to post
2 hours ago, strike said:

No point in posting the log if everything is working. Maybe the vpn server you connected to had issues. You won't be able to see the webui before the vpn tunnel is up. 

I have no idea why. The VPN userver I use never had issue anytime. It was working when I used PrivateVPN client, but docker webUI just would not start. Anyways, for some reason, after turnning on debug mode, it works now.

Link to post
17 hours ago, strike said:

No point in posting the log if everything is working. Maybe the vpn server you connected to had issues. You won't be able to see the webui before the vpn tunnel is up. 

I think I know what the real problem is. TLDR, when I access my home network via openVPN, delugeVPN with VPN on will not load webUI.

When I reported the issue, I was at work, using VPN from my home router to work on unraid dockers, and delugevpn webUI will not load, returns "ERR_CONNECTION_TIMED_OUT". My radarr and donarr can both see deluge working.

When I followed the steps to turn on debug mode, I was at home on my local network. webUI loaded correctly.

I am at work now, and webUI will not load, and returns "ERR_CONNECTION_TIMED_OUT". Radarr and sonarr can see deluge just fine. I launched chromium docker, and from that browser, deluge webUI loaded without any issue.

Link to post
13 minutes ago, jiyang1018 said:

when I access my home network via openVPN, delugeVPN with VPN on will not load webUI.

this is because your VPN allocated ip will not be in the LAN_NETWORK range and thus blocked, you need to add in your vpn network range AND your lan range to LAN_NETWORK if you need access from both (hint use comma to separate the values).

Link to post
6 minutes ago, binhex said:

this is because your VPN allocated ip will not be in the LAN_NETWORK range and thus blocked, you need to add in your vpn network range AND your lan range to LAN_NETWORK if you need access from both (hint use comma to separate the values).

Added a new range in LAN_NETWORK, and it is working now. Thanks.

I also added work IP to that and I can access deluge via URL.

Edited by jiyang1018
Link to post

My apologies if this is an issue that has been dealt with but, scanning back through the past few pages I haven’t come across a solution. However it is similar to many issues. 
 

I set up delugevpn per spaceinvaderone’s video on How to route any docker container through a VPN. 
 

I am trying to route my binhex-sabnzbd through deluge. I followed his steps and I can `curl ifconfig.io` to see that binhex-sabnzbd is in fact routing through the VPN properly. 
 

Now I can’t see the WebUI. I came across the Q&A and tried to follow Q25-27 and set up the containers according. But I still have no luck. My first question is what do you mean to set the VPN container to localhost instead of Lan IP? How is that accomplished? I have deluge set to Bridge. If I set it to host it returns an error about the extra parameters not being allowed. 

Network is 192.168.4.0/24

Server is 

I have deleted the port:8989 (had to change from 8080 due to conflicts) from my  binhex-sabnzbd container and added --net=container:binhex-delugevpn and made the network None. 
 

In deluge I have privoxy Yes, I added 8989 to VPN_INPUT_PORTS and added a port variable at the end for 8989. 
 

When I try and access <server-ip>:8989 with another pc on the network I get a 503 splash screen. Says the privoxy on (172.17.xx.xx) port 8118 enabled. Then it says the connection could not be established. 
 

I feel like this is going to be a simple settings issue. Thank you for any help. 
 

EDIT:

The error 503 was because I proxied my internet browser with deluge. 
 

The current issue is that the WebUI does not display. It returns ERR_CONNECTION_REFUSED. 

Edited by wortzinator
Link to post
On 6/12/2021 at 6:47 PM, strike said:

When you read the faq to get the webui working it didn't occur to you to continue reading it? See Q27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

That isn't my problem. That's a solution for having containers inside the VPN network connect with containers outside the VPN network.

 

My problem is that containers inside the VPN network aren't even connected to the internet, let alone the VPN.

 

I also don't understand this part of the FAQ:

 

Quote

The other change you will need to do is when defining connections from an application to another application in the same VPN container network then you will need to set the host to 'localhost' and NOT the LAN IP address, this is because the applications are now bound to the same network and thus should communicate over 'localhost'.

Set the "host to localhost"? What host? Where?

Edited by Stubbs
Link to post
35 minutes ago, Stubbs said:

Set the "host to localhost"? What host? Where?

host is the host field in sonarr/radarr/etc and 'localhost' is a set name that all containers have, it means the ip address of the machine the application is running on (127.0.0.1), an example screenshot from my sonarr instance demonstrating this, note the 'Host' field:-

image.thumb.png.cb587c84afc66fc7f5fdd17fde0036c7.png

Link to post
29 minutes ago, binhex said:

host is the host field in sonarr/radarr/etc and 'localhost' is a set name that all containers have, it means the ip address of the machine the application is running on (127.0.0.1), an example screenshot from my sonarr instance demonstrating this, note the 'Host' field:-

image.thumb.png.cb587c84afc66fc7f5fdd17fde0036c7.png

Do you set the application to localhost before you remove all of the ports from the docker template? I am not able to enter the WebUI in order to enter this value once I remove the ports even after adding the WebUI ports to the correct spots in the Deluge template. 
 

Link to post

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.