[Support] binhex - DelugeVPN


Recommended Posts

I have multiple containers passing through delugevpn and everything is working fine.  I would like to pass a separate container through to a different VPN address.  Does anyone know how I can do this?   I tried using another vpn container but it wants to use port 8118 also and when I change the port in the second container to something else I cannot access it.

Link to comment
19 hours ago, Simmer said:

Hello there! I recently lost the ability to access my UI on deluge. I have been wanting to switch to qbit anyway so I deployed binhex' qbit-vpn container but have the same exact issue. I am not sure if it was due to recent container update or not, as I haven't accessed container in a week or so but up until this point it was fine. Browser error states timeout/busy.

Attached is my supervisord.log for deluge (did not attach qbit, since diff thread and maybe I can use solution for both)

 

Thanks!

supervisord.log 40.33 kB · 1 download

whats the ip address of the machine running the web browser that you are using to attempt connection to the deluge web ui?.

Link to comment
14 hours ago, Marino13 said:

but it wants to use port 8118 also and when I change the port in the second container to something else I cannot access it.

are you changing the host port or the container port?, it should (nearly) ALWAYS be host side only, each port must be unique and not used by any other containers, that will then allow you to start two vpn containers.

Link to comment
7 hours ago, binhex said:

are you changing the host port or the container port?, it should (nearly) ALWAYS be host side only, each port must be unique and not used by any other containers, that will then allow you to start two vpn containers.

Thanks.  Yes, just the host port.  I guess I was doing it correctly and it was working but I was being a bonehead thinking that if the web_ui for privoxy wasn't coming up that it wasn't working.  Once I installed it again, did an ifconfig.io and saw the correct IP I tried adding another container though it and it worked.  

Link to comment

I recently (2 days ago) moved my unraid 6.9.2 server to another subnet on my network; from 192.168.1.143 to 192.168.2.143. I likewise changed the ip of the delugevpn container from 192.168.1.144 to 192.168.2.144. Since the move, I have been unable to access the webgui of the delugevpn container unless I am accessing it from the same subnet. However, the move didn't affect access to the unraid webgui at 192.168.2.143 or the plex container at 192.168.2.145. Using ifconfig on the delugevpn console showed the correct netmask and gateway. I'm not sure what to do at this point except for reinstalling it. Any help would be appreciated. 

 

***EDIT***

 

I think my issue may be related to the in-built iptables rules within the delugevpn container?

 

 

tower-diagnostics-20220324-1549.zip

Edited by whirledpeaz
possible answer found
Link to comment

If the container is running about half an hour to an hour the privoxy service is getting really slow and later not usable at all.


I enabled some of the privoxy debug settings and found messages like: 

/config/privoxy/logfile
2022-03-24 21:06:55.135 1465599df180 Error: Rejecting connection from 193.57.40.8. Maximum number of connections reached.
2022-03-24 21:06:55.203 1465599df180 Error: Rejecting connection from 46.161.27.177. Maximum number of connections reached.
2022-03-24 21:06:55.204 1465599df180 Error: Rejecting connection from 46.161.27.177. Maximum number of connections reached. 

So i tried to increase 'max-client-connections' to over 1024 but this doesn't help, its just delaying the slowdown.

After enabling more of the debug settings i found something wired, it looks like many other ppl using my privoxy:

Spoiler

185.105.116.116 - - [26/Mar/2022:11:10:51 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=785E4A5A1FDEE3C676636267BFF41850&steamids=76561198068674229 HTTP/1.1" 200 329
91.199.118.174 - - [26/Mar/2022:11:10:52 +0100] "CONNECT 212.227.17.178:993 HTTP/1.1" 200 4846
91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT www.bing.com:443 HTTP/1.1" 200 174001
91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT 212.227.17.178:993 HTTP/1.1" 200 4846
91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT redsky.target.com:443 HTTP/1.1" 200 6499
142.132.224.0 - - [26/Mar/2022:11:10:54 +0100] "CONNECT steamcommunity.com:443 HTTP/1.1" 200 3986
91.199.118.174 - - [26/Mar/2022:11:10:54 +0100] "CONNECT www.amazon.com:443 HTTP/1.1" 200 8853
77.223.113.54 - - [26/Mar/2022:11:10:54 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=BDFAA0B48EFB3785A044B35C421423BF&steamids=76561198807819327 HTTP/1.1" 200 341
91.199.118.174 - - [26/Mar/2022:11:10:54 +0100] "CONNECT www.walmart.com:443 HTTP/1.1" 200 15160
91.199.118.174 - - [26/Mar/2022:11:10:55 +0100] "CONNECT allegro.pl:443 HTTP/1.1" 200 5843
142.132.224.0 - - [26/Mar/2022:11:10:55 +0100] "GET http://api.steampowered.com/ISteamUser/GetFriendList/v1/?key=DD92DA7247D10B6B2330C7ED97C6CD9A&steamid=76561198998915288 HTTP/1.1" 200 245
91.199.118.174 - - [26/Mar/2022:11:10:55 +0100] "CONNECT 52.98.151.82:993 HTTP/1.1" 200 4423
149.154.117.169 - - [26/Mar/2022:11:10:55 +0100] "CONNECT o2.mail.ru:443 HTTP/1.1" 200 4089
149.154.117.169 - - [26/Mar/2022:11:10:56 +0100] "CONNECT o2.mail.ru:443 HTTP/1.1" 200 4089
91.199.118.174 - - [26/Mar/2022:11:10:56 +0100] "CONNECT t.me:443 HTTP/1.1" 200 15661
91.199.118.174 - - [26/Mar/2022:11:10:56 +0100] "CONNECT outlook.office365.com:993 HTTP/1.1" 200 4401
185.105.116.116 - - [26/Mar/2022:11:10:56 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=E98F71799ABDF712BB9A87DCFAB8F020&steamids=76561198823641533 HTTP/1.1" 200 351
77.223.113.54 - - [26/Mar/2022:11:10:57 +0100] "CONNECT steamcommunity.com:443 HTTP/1.1" 200 4025
193.108.113.6 - - [26/Mar/2022:11:10:57 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=070149BA46D4B1BD19FEDBC6C160A33E&steamids=76561198798735736 HTTP/1.1" 200 265
95.216.42.199 - - [26/Mar/2022:11:10:57 +0100] "CONNECT texas.savvyatfirstbanklubbock.com:443 HTTP/1.0" 200 4172
20.73.244.41 - - [26/Mar/2022:11:10:58 +0100] "CONNECT api.ivi.ru:443 HTTP/1.0" 200 4668 

 

There thousands of these messages in the log.
If i restart the container it takes again half an hour to an hour till all these messages appear again.

It always starts with a request similar to this one:

2022-03-24 21:52:47.755 15320cde6640 Header: scan: CONNECT check.best-proxies.ru:443 HTTP/1.1
2022-03-24 21:52:47.756 15320cde6640 Header: scan: Host: check.best-proxies.ru:443
2022-03-24 21:52:47.756 15320cde6640 Header: scan: Proxy-Connection: keep-alive
2022-03-24 21:52:47.756 15320cde6640 Header: scan: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
2022-03-24 21:52:47.756 15320cde6640 Header: crumble crunched: Proxy-Connection: keep-alive!
2022-03-24 21:52:47.757 15320cde6640 Request: check.best-proxies.ru:443/ 



I tried to adjust the iptables by my self but i dont get it working. 

Any advise how I can prevent the internet from connecting to my privoxy container?
I doesn't want it to be visible/connectable from outside my local network.
 







 

Link to comment
If the container is running about half an hour to an hour the privoxy service is getting really slow and later not usable at all.

I enabled some of the privoxy debug settings and found messages like: 
/config/privoxy/logfile2022-03-24 21:06:55.135 1465599df180 Error: Rejecting connection from 193.57.40.8. Maximum number of connections reached.2022-03-24 21:06:55.203 1465599df180 Error: Rejecting connection from 46.161.27.177. Maximum number of connections reached.2022-03-24 21:06:55.204 1465599df180 Error: Rejecting connection from 46.161.27.177. Maximum number of connections reached. 

So i tried to increase 'max-client-connections' to over 1024 but this doesn't help, its just delaying the slowdown.

After enabling more of the debug settings i found something wired, it looks like many other ppl using my privoxy:
Spoiler

185.105.116.116 - - [26/Mar/2022:11:10:51 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=785E4A5A1FDEE3C676636267BFF41850&steamids=76561198068674229 HTTP/1.1" 200 329
91.199.118.174 - - [26/Mar/2022:11:10:52 +0100] "CONNECT 212.227.17.178:993 HTTP/1.1" 200 4846
91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT www.bing.com:443 HTTP/1.1" 200 174001
91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT 212.227.17.178:993 HTTP/1.1" 200 4846
91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT redsky.target.com:443 HTTP/1.1" 200 6499
142.132.224.0 - - [26/Mar/2022:11:10:54 +0100] "CONNECT steamcommunity.com:443 HTTP/1.1" 200 3986
91.199.118.174 - - [26/Mar/2022:11:10:54 +0100] "CONNECT www.amazon.com:443 HTTP/1.1" 200 8853
77.223.113.54 - - [26/Mar/2022:11:10:54 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=BDFAA0B48EFB3785A044B35C421423BF&steamids=76561198807819327 HTTP/1.1" 200 341
91.199.118.174 - - [26/Mar/2022:11:10:54 +0100] "CONNECT www.walmart.com:443 HTTP/1.1" 200 15160
91.199.118.174 - - [26/Mar/2022:11:10:55 +0100] "CONNECT allegro.pl:443 HTTP/1.1" 200 5843
142.132.224.0 - - [26/Mar/2022:11:10:55 +0100] "GET http://api.steampowered.com/ISteamUser/GetFriendList/v1/?key=DD92DA7247D10B6B2330C7ED97C6CD9A&steamid=76561198998915288 HTTP/1.1" 200 245
91.199.118.174 - - [26/Mar/2022:11:10:55 +0100] "CONNECT 52.98.151.82:993 HTTP/1.1" 200 4423
149.154.117.169 - - [26/Mar/2022:11:10:55 +0100] "CONNECT o2.mail.ru:443 HTTP/1.1" 200 4089
149.154.117.169 - - [26/Mar/2022:11:10:56 +0100] "CONNECT o2.mail.ru:443 HTTP/1.1" 200 4089
91.199.118.174 - - [26/Mar/2022:11:10:56 +0100] "CONNECT t.me:443 HTTP/1.1" 200 15661
91.199.118.174 - - [26/Mar/2022:11:10:56 +0100] "CONNECT outlook.office365.com:993 HTTP/1.1" 200 4401
185.105.116.116 - - [26/Mar/2022:11:10:56 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=E98F71799ABDF712BB9A87DCFAB8F020&steamids=76561198823641533 HTTP/1.1" 200 351
77.223.113.54 - - [26/Mar/2022:11:10:57 +0100] "CONNECT steamcommunity.com:443 HTTP/1.1" 200 4025
193.108.113.6 - - [26/Mar/2022:11:10:57 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=070149BA46D4B1BD19FEDBC6C160A33E&steamids=76561198798735736 HTTP/1.1" 200 265
95.216.42.199 - - [26/Mar/2022:11:10:57 +0100] "CONNECT texas.savvyatfirstbanklubbock.com:443 HTTP/1.0" 200 4172
20.73.244.41 - - [26/Mar/2022:11:10:58 +0100] "CONNECT api.ivi.ru:443 HTTP/1.0" 200 4668 

 
There thousands of these messages in the log.
If i restart the container it takes again half an hour to an hour till all these messages appear again.

It always starts with a request similar to this one:

2022-03-24 21:52:47.755 15320cde6640 Header: scan: CONNECT check.best-proxies.ru:443 HTTP/1.12022-03-24 21:52:47.756 15320cde6640 Header: scan: Host: check.best-proxies.ru:4432022-03-24 21:52:47.756 15320cde6640 Header: scan: Proxy-Connection: keep-alive2022-03-24 21:52:47.756 15320cde6640 Header: scan: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.02022-03-24 21:52:47.756 15320cde6640 Header: crumble crunched: Proxy-Connection: keep-alive!2022-03-24 21:52:47.757 15320cde6640 Request: check.best-proxies.ru:443/ 



I tried to adjust the iptables by my self but i dont get it working. 

Any advise how I can prevent the internet from connecting to my privoxy container?
I doesn't want it to be visible/connectable from outside my local network.
 






 

Are you port forwarding the port used by privoxy on your router? If so remove it, if not then I can only assume that your VPN provider is exposing all inbound ports for your connection, simplest solution would be to switch VPN provider in that case.

Sent from my CLT-L09 using Tapatalk

Link to comment

Thank you for the quick reply. 

My router is only exposing 80 and 443.

 

Yes my VPN is exposing all inbound ports. The VPN provider has a Feature called NAT-Firewall, when enable noone is able to connect to me. That means deluge leeches but is not seeding.

 

Is there any way to do this with iptabels?

Are other VPN providers have more control about exposing inbound ports?

Link to comment
Thank you for the quick reply. 
My router is only exposing 80 and 443.
 
Yes my VPN is exposing all inbound ports. The VPN provider has a Feature called NAT-Firewall, when enable noone is able to connect to me. That means deluge leeches but is not seeding.
 
Is there any way to do this with iptabels?
Are other VPN providers have more control about exposing inbound ports?
Most VPN providers are very strict when it comes to inbound ports, opening up all ports is unusual. I would recommend mullvad, pia, or airvpn, pia if you want an easy time.

Sent from my CLT-L09 using Tapatalk

Link to comment

Hi there,

I hope you can point me in the correct direction.  I'm using binhex/delugevpn with great success, except for a healthcheck working properly.  I believe the issue is related to the inabilty to resolve the names of other containers.

 

For a healthcheck i am using:  curl http://<other_container_name>:8888/api/health?apiKey=secret_api_key 2>&1 | grep -q error ;if [ "$$?" -eq 1 ]; then exit 0; else exit 1; fi

 

This fails.  When I attempt to do an nslookup <other_container_name> I get 

nslookup <other_container_name>
Server:         84.200.69.80
Address:        84.200.69.80#53

** server can't find <other_container_name>: NXDOMAIN

 

How can I get local name resolution, please?

Link to comment

Hey @binhex thank you for the ongoing support of this container, it's excellent.

 

I recently switched to using Prowlarr and have it set to use Deluge's VPN connection. I have followed the FAQs to add the ports to `VPN_INPUT_PORTS` so that I can access it via its web UI. I have added the ports for Sonarr and Radarr to `VPN_OUTPUT_PORTS` but I cannot seem to get Prowlarr to connect. Radarr / Sonarr can connect successfully to prowlarr but not the other way around.

I have tried using radarr's container ip address (eg 172.18.0.5) and I have also tried with the docker gateway (172.17.0.1) without luck.

 

I've read though many pages of comments on here but still can't figure it out.

Any advice very welcome!

 

SOLVED:

I had to use http://172.18.0.1:7878/radarr as the ip address for Radar. I'm not sure what network that is or why it needs /radarr at the end but it works now. Spotted this address in the graphs section.

Edited by darksupernova
solved
Link to comment

Evening all,

 

I've just set up this docker but am having trouble getting the vpn aspects to work. If I turn the VPN to "off", the docker works just fine, so I know that its just the VPN side of things. When I turn on the vpn, I can't access the GUI at all, but can as soon as I turn it off. I have a subscription with PureVPN, and downloaded the ovpn file for the server i need to use (as per SpaceInvaderOne's youtube guide). However, I can't see any certificates (crt or pem) files anywhere on the purevpn web pages. I had a quick look through the log and can't see anything that looks out of place, but I'm not really sure what I'm looking for to be honest!

 

Sorry for the really bone question: but how do I work out what is wrong and how do I get it working?! Cheers.

Edited by PitRejection2359
typo
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.