[Support] binhex - DelugeVPN


Recommended Posts

23 minutes ago, Burizado said:

Is this only for the new updated Deluge setup?

due to tightening of iptables its now a requirement to use localhost WHEN routing containers through the same network, however its really highlighting a bad configuration, as previously mentioned you should be using localhost, no point in sending outbound traffic to your host for it only to be routed back again!.

Link to comment
13 minutes ago, JimmyGerms said:

but was curious if there was a way to set the Host within the Jackett docker?

i dont really follow sorry, the way i would do it is set sonarr and radarr to talk to jackett using localhost again, this is the correct way to do it (assuming jackett, sonarr, radarr, and your download client are all using the same network).

Link to comment

Sorry, I ended up deleting that post and moved it to the proper thread. Didn't mean to bog down the thread. I can explain a bit more over there maybe? But for now I've just replaced the '192.168.1.blah' with 'localhost' after clicking on the copy buttons. Think we're back! Thank you so much for the help! I get it a bit more now.

Link to comment

I'm running your latest docker image on my Synology D916+ and am now receiving following error message in the supervisord.log:

FATAL: kernel too old

 

I'm not using Wireguard or anything. Possible something you added in this latest one isn't compatible with our older kernel?

 

Edit: returned to 2.0.4.dev38_g23a48dd01-3-01 and all is good again. Let me know if I can test anything.

Edited by NGDM
  • Like 1
Link to comment
8 hours ago, binhex said:

IMPORTANT:- As part of the tightening up if you run multiple containers through a single vpn container then please ensure you define all web ui ports (if more than 1 port then use comma to separate) for all routed containers in 'ADDITIONAL_PORTS' env var for the vpn container.

 

I ran the manual force update.  I am not seeing the 'ADDITIONAL_PORTS' var in the docker config in unRAID, but I did see it in the logs when I started Deulge.  Do we need to add it manually in the unRAID config for the docker, or specify it in the 'Extra Parameters' section?

Link to comment

Sorry for the barrage of questions.

 

I also setup my Windows 10 VM to use the DelugeVPN connection by setting it up according to Spaceinvader's video.  Is there a way to route the VM through the DelugeVPN with this new update?  I was not sure if I needed to add a port to the 'ADDITIONAL_PORTS' var and if so what port.

 

Image from Internet Options > Connections tab > LAN settings inside my Win 10 VM.

2021-02-25 17_51_03-Window.png

Link to comment

I'm also unable to use "localhost" in Sonarr/Radarr/etc. Setting them to the app IP of 172.17.x.x works. I'm also still having DNS leaks with a Firefox proxy pointing at DelugeVPN as detailed here. Everything, including DelugeVPN, is set to Network type = Bridge in the container settings. Sonarr, Radarr, NZBHydra2, Jackett, etc., are all using HTTP proxy with 172.17.x.x:8118 and "bypass local network" turned on. This may be the wrong way to use DelugeVPN with other containers, I'm not sure. 

 

I'm also now getting this in my log over and over, even though everything seems to be working if you ignore the DNS leak.

2021-02-25 17:25:10,431 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2021-02-25 17:25:10,432 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2021-02-25 17:25:10,433 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-02-25 17:25:11,444 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2021-02-25 17:25:11,449 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2021-02-25 17:25:11,449 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is XXXXXX
[debug] Deluge IP is XXXXXX

2021-02-25 17:25:41,451 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2021-02-25 17:25:41,481 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.1.4'

2021-02-25 17:25:41,482 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2021-02-25 17:25:41,490 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2021-02-25 17:25:41,502 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2021-02-25 17:25:41,503 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

<repeat forever>

 

Link to comment

I just updated this container, and now I cannot connect Unraid local IP or to any of my dockers running on Unraid using the IP/port combo when I have DelugeVPN set as my proxy address/port. This worked right before the update.

 

Is there something I need to update/change?

 

EDIT: I'm also getting errors in Sonarr and Radarr that it can't connect to Jackett:

image.thumb.png.1e54cdcd95697e2e69eb0d436c930a3f.png

image.thumb.png.97e07e1dda7ce02f72157e1e4b3c691d.png

 

What's interesting is I can use public IPs and resolve public domains just fine using the proxy. It's just local addresses.

 

EDIT 2: I'm pretty sure I've added all the corrected settings, but it's still not working. Any ideas? If I can't fix it, can anyone tell me how to roll it back to the previous version? If I set my PC to use the deluge proxy, I can't even connect to the Unraid web UI anymore.

 

ADDTIONAL_PORTS:
image.thumb.png.dc7eb84a2f91451e9f8f69987217c2b5.png

 

Jackett:

image.png.222398d18291756b3fc12b735225f355.png

 

Radarr:

image.png.a7a1815599b14f59a46dcf23553aef2c.png

image.png.748a711bf9cd25bc914104d503ab4e2b.png

 

Sonarr:

image.png.d95e5212e0cb641a8c512e596ef0751a.png

image.png.aedab958e72949dbd640a01ca4acc87d.png

 

 

DOCKERS (deluge is showing previous version because I already rolled it back before I got screenshot):

image.thumb.png.a5e2a380ccc1c998d4ca94553bd1d8fa.png

image.png.170b131eead5c8f65834267541e61349.png

Edited by carnivorebrah
  • Like 2
Link to comment
43 minutes ago, carnivorebrah said:

I just updated this container, and now I cannot connect Unraid local IP or to any of my dockers running on Unraid using the IP/port combo when I have DelugeVPN set as my proxy address/port. This worked right before the update.

 

Is there something I need to update/change?

 

EDIT: I'm also getting errors in Sonarr and Radarr that it can't connect to Jackett:

image.thumb.png.1e54cdcd95697e2e69eb0d436c930a3f.png

image.thumb.png.97e07e1dda7ce02f72157e1e4b3c691d.png

 

What's interesting is I can use public IPs and resolve public domains just fine using the proxy. It's just local addresses.

 

I had same trouble with update done today. Tried to read few pages here and nothing worked. Finally rolled back to 2.0.4 dev38 and its golden again...

  • Like 1
Link to comment
56 minutes ago, jpcom said:

 

I had same trouble with update done today. Tried to read few pages here and nothing worked. Finally rolled back to 2.0.4 dev38 and its golden again...

I'm going to give it another day to see if I can figure out how to make things work again.  If I can't, I'm going to look into how I can rollback DelugeVPN as you have  I am hoping a nights sleep will help me pull together and understand what I have been reading this forum.

Edited by storagehound
clarity
Link to comment

Hi, sorry another person getting stuck with this new update here. Not really that great with unraid so guessing something maybe setup wrong in the first place which is why its not not working. (but has been fine for 2 years ish)

Didn't have additional_ports so added this:

image.png.d353aa5df08fcc4cfaf97c026420144e.png

Assume that's correct?

 

Sonarr/Radarr/Jacket all on same IP as deluge.  Get this error in those when trying to test download client Unknown exception: The operation has timed out.: 'http://192.168.10.10:8112/json'

I have the host in Sonarr/Radarr/Jacket set to the same IP as deluge/server, tried localhost and it instantly says unable to connect on test.

Also tried setting the proxy to localhost but no change to test results

 

 

Link to comment
2 hours ago, jpcom said:

 

I had same trouble with update done today. Tried to read few pages here and nothing worked. Finally rolled back to 2.0.4 dev38 and its golden again...

Just curious, how do you go about rolling back to the previous version?

I looked through the Github and Dockerhub for the information, but not finding it.

Link to comment

I think I got it.  Seeing this screenshot  from torlh helpd turn on a few brain cells.  There were multiple steps to be done.
I searched for "ADDITIONAL_PORTS" and found Binhex's entry in another forum.   So many steps.


UGLY DIRECTIONS FOLLOW:

1)  I routed Jackett, Sonarr and Radarr (all Binhex versions) through Deluge VPN.  Following Spaceinvader one's Youtube tutorial How to route any docker container through a VPN container will get you most the way there (Link below).  But you'll need to add the "ADDITONAL_PORTS" variable if your Deluge-VPN template does not already have it.  I'll screenshot mine.  Those 3 values you see are Jackett, Radarr & Sonarr.  This will allow you to access them in the browser (remember, follow the video first).
image.png.8d4e26473ea23f39ec10b53ed196eb11.png

 

2)  Once you are able to access your webpages you should go through them and remove any explicit host name for your server (like 192.167.1.11) and replace it with Localhost.  I would start with Jackett (if you are using that) since you may have other programs pointing to it.  In the case of Radar I had to do this for all of my indexers,  the Proxy settings under General and for the Download Client.  Here's a screenshot of my doing the "Download Client" in Radar. 
image.thumb.png.402eef5bc0d84eefe6e9b6d1e2168288.png

 

After I had done all of this my containers were able to be accessed by the web page with the appropriated port:  http://192.xxx.x.12:9117 for Jackett and etc.  I saw that Radarr and Sonarr were able to access their indexers and deluge vpn. 

I know these directions are not great.  I am exhausted.  I only did it for those of you who will be driving yourself crazy and just need a hint.  I know one of our better explainer will probably put something more useful and cohesive together. 

Thank you Binhex and Torlh for giving me enough to figure  out what to do and actually clean up my sever.

2 hours ago, Torih said:

Hi, sorry another person getting stuck with this new update here. Not really that great with unraid so guessing somethi
ng maybe setup wrong in the first place which is why its not not working. (but has been fine for 2 years ish)

Didn't have additional_ports so added this:

image.png.d353aa5df08fcc4cfaf97c026420144e.png

Assume that's correct?

 

Sonarr/Radarr/Jacket all on same IP as deluge.  Get this error in those when trying to test download client Unknown exception: The operation has timed out.: 'http://192.168.10.10:8112/json'

I have the host in Sonarr/Radarr/Jacket set to the same IP as deluge/server, tried localhost and it instantly says unable to connect on test.

Also tried setting the proxy to localhost but no change to test results

 

 

 

Edited by storagehound
A little cleanup
  • Thanks 2
Link to comment
32 minutes ago, storagehound said:

I think I got it. 

 

Yes!  I think I stumbled on it too, then I came here and saw your post.

 

I remember SpaceinvaderOne had a video similar to what was being described and found the video you linked.

Putting that together with the steps in Q24 on the VPN FAQ doc helped too.

 

What's not mentioned in the video or FAQ is I had to change my downloader entry in Radarr to 'localhost'.

Link to comment
4 hours ago, MammothJerk said:

Wait so to clarify:

for dockers to make use of the delugevpn privoxy (and even the download client for radarr/sonarr/lidarr) they must have "--net=container:Binhex-DelugeVPN" in their extra parameters?

No.

You can use privoxy from any other docker or computer on your network by simply configuring the proxy settings of the application/computer to point to the privoxy address:port. For example, you would do this under settings in the Radarr Web UI. Or in Firefox proxy setting on you normal PC.
But for dockers running on you unraid server, like radarr/sonarr/lidarr, there is an alternative way. You can make the other docker use the same network as deluge, by adding the net=container...  into the extra parameters. It has some benefits in that you are guaranteed that all docker application traffic goes via the VPN. When using privoxy, only http traffic is routed via the VPN, and only if the application itself has implemented the proxy function properly.

 

But doing it the net=container way, you shouldn't also use the proxy function in the application itself.

So one or the other, depending on your use case and needs, but not both.

  • Thanks 1
Link to comment
5 hours ago, MammothJerk said:

Wait so to clarify:

for dockers to make use of the delugevpn privoxy (and even the download client for radarr/sonarr/lidarr) they must have "--net=container:Binhex-DelugeVPN" in their extra parameters?

hmm im seeing a lot of this, the answer is a definite NO!, for everybody here:-

 

ADDITIONAL_PORTS and the 'Extra Parameter' value of '--net=container:<name of vpn container>' is ONLY required if you are routing other containers through a vpn container, if you are settings your application to use the proxy (privoxy) then this is NOT the case.

Link to comment
1 hour ago, binhex said:

hmm im seeing a lot of this, the answer is a definite NO!, for everybody here:-

 

ADDITIONAL_PORTS and the 'Extra Parameter' value of '--net=container:<name of vpn container>' is ONLY required if you are routing other containers through a vpn container, if you are settings your application to use the proxy (privoxy) then this is NOT the case.

So if just using privoxy from radarr/sonarr etc we dont need to change anything? Because nothing using privoxy is working since the update to deluge.

  • Like 2
Link to comment
26 minutes ago, Torih said:

So if just using privoxy from radarr/sonarr etc we dont need to change anything? Because nothing using privoxy is working since the update to deluge.

i need more details, please screenshot your sonarr and radarr settings for a start, a few questions for you to answer too:-

 

1. are you routing any containers through a vpn container, if so which ones?

2. have you defined LAN_NETWORK for your vpn container, if so what is it and what is your servers ip address?

3. are you using custom bridge, staitc ip addresses or maclvlan for any of your containers? if so which ones and what are the values of each?.

Link to comment

I got it to work thanks to Spaceinvader's Video and the VPN FAQ Instructions Q24 at the bottom.  Essentially I followed the video, added the 'ADDITIONAL_PORTS' variable, and then just updated the settings inside Radarr for example to be 'localhost' for Download Clients (Deluge) and Indexers (Jackett).

 

One thing I am noticing is that the containers I change will not connect to Plex Media Server any more.  This makes sense since all the dockers using the VPN have an IP address outside my network now, when I use 'curl ifconfig.io' in their consoles.  For those that have this setup working, do you have an issue with containers not connecting to others not using the VPN?

 

This is my setup for Plex in Radarr, under the Connect settings.  I could route my Plex container through the VPN but then I am guessing anything I direct play will go out through the VPN and back to my TV.

2021-02-26 07_41_16-Window.png

Edited by Burizado
Link to comment
29 minutes ago, binhex said:

i need more details, please screenshot your sonarr and radarr settings for a start, a few questions for you to answer too:-

 

1. are you routing any containers through a vpn container, if so which ones?

2. have you defined LAN_NETWORK for your vpn container, if so what is it and what is your servers ip address?

3. are you using custom bridge, staitc ip addresses or maclvlan for any of your containers? if so which ones and what are the values of each?.

I posted screenshots of my setup a few posts up. Please let me know if you need more screenshots

 

1. Yes, I am routing Radarr, Sonarr and Jackett through DelugeVPN using the web GUI settings for each docker to point to the deluge container IP/port (10.100.1.3:8118). I tried using "localhost" too, but it wouldn't connect.

2. Yes, my unraid server IP is 10.100.1.3, and my LAN_NETWORK is defined as 10.100.1.0/24.

image.thumb.png.5cca5fbe90f3f864f6bcfe4a673a9cc9.png

3. Yes, I have a couple containers set with static IPs (pihole and guacamole) that I can no longer access when I point a physical device to the deluge proxy. Containers using my "proxynet" vlan work fine. When I try to connect to the Unraid web gui using a physical device pointed to the proxy IP/port, it gives me a privoxy error.

 

I will try to go through it again and get more screenshots of all of the errors, but tempted to just wait.

Edited by carnivorebrah
  • Thanks 1
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.