[Support] binhex - DelugeVPN


Recommended Posts

On 3/23/2020 at 4:05 AM, tehtide said:

I've got both networks in there. I'm able to ping the deluge docker VPN from both networks, but radarr/sonarr won't connect to the json feed if they are on the same network.


Unknown exception: The operation has timed out.: 'http://10.10.50.22:8112/json'

 

@tehtid, did you ever fix this or anyone else know how to get it working? I'm having the exact same issue.

Something stranger is that the VPN port (8118) works but the Deluge port (8112) doesn't work. I'm testing by telnet'ing to the port from the Sonarr docker. Telnet was installed by issuing `pacman -S inetutils` after connecting to the Docker's console.

 

I tested the other port (58846) and that one connects. For some reason 8112 won't connect.

image.thumb.png.6bde6b6a9779ed952849c386458a74b2.png

 

 

Connects fine from other networks (eg: my laptop)

image.thumb.png.ddf7938a7766a150bba3a2d20384a758.png

 

 

If I set vpn to off in delugevpn, the Sonarr docker can now reach 8112/tcp on delvugevpn. My laptop can still connect to delugevpn on 8112/tcp.

image.thumb.png.5b82e8ede4b921a540b74b960ec73d86.png

 

Edited by MrLinux
Clarified which docker I was trying to telnet from to test the port
Link to comment
7 hours ago, xxDeadbolt said:

Why did you have to restart it, what's happening (logs?) ? 

I was away for the weekend and come home and Deluge wasn't gui wasn't loading, showed it was trying to connect over and over.  

 

Logs show now "Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed"

 

Edited by djgizmo
Link to comment
17 hours ago, djgizmo said:

I was away for the weekend and come home and Deluge wasn't gui wasn't loading, showed it was trying to connect over and over.  

 

Logs show now "Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed"

 

I think there may have been an issue with that before but, if memory serves, Binhex said it was fixed. You definitely on the latest container version? Using legacy or nextgen servers for PIA?

Link to comment
17 hours ago, djgizmo said:

I was away for the weekend and come home and Deluge wasn't gui wasn't loading, showed it was trying to connect over and over.  

 

Logs show now "Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed"

 

yeah thats something for me to look at as it looks like something has changed on the remote site, however it will fall back to the next website to check for incoming port so that is not the issue, most probably you havent switch to next-gen and thus you are seeing the crumbling legacy-gen network issues.

Link to comment
On 9/29/2020 at 8:11 AM, Geran said:

Thank you. That's what I originally did after removing the test tag but I just did it again and it is working now.

 

On 9/29/2020 at 8:11 AM, Geran said:

Thank you. That's what I originally did after removing the test tag but I just did it again and it is working now.

Can someone explain how to do a 'force update'?   I'm having the same issue that my OpenVPN won't connect with Port Forwarding....   Thanks

Link to comment
17 minutes ago, cerickso88@gmail.com said:

 

Can someone explain how to do a 'force update'?   I'm having the same issue that my OpenVPN won't connect with Port Forwarding....   Thanks

Toggle advanced view in the top right section of the Docker page and then click force update on whichever docker container you'd like to update.

Link to comment
@tehtid, did you ever fix this or anyone else know how to get it working? I'm having the exact same issue.
Something stranger is that the VPN port (8118) works but the Deluge port (8112) doesn't work. I'm testing by telnet'ing to the port from the Sonarr docker. Telnet was installed by issuing `pacman -S inetutils` after connecting to the Docker's console.
 
I tested the other port (58846) and that one connects. For some reason 8112 won't connect.
image.thumb.png.6bde6b6a9779ed952849c386458a74b2.png
 
 
Connects fine from other networks (eg: my laptop)
image.thumb.png.ddf7938a7766a150bba3a2d20384a758.png
 
 
If I set vpn to off in delugevpn, the Sonarr docker can now reach 8112/tcp on delvugevpn. My laptop can still connect to delugevpn on 8112/tcp.
image.thumb.png.5b82e8ede4b921a540b74b960ec73d86.png
 

Anyone happen to know how to fix this? Thanks


Sent from my iPhone using Tapatalk
Link to comment

My DelugeVPN has been doing this for the last three hours:

2020-10-07 16:02:16,782 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 16:05:31,503 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 16:05:34,161 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 16:06:16,034 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 16:17:17,602 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 16:20:32,324 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 16:20:34,978 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 16:21:16,850 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 16:32:18,421 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 16:35:33,138 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 16:35:35,798 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 16:36:17,667 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 16:47:19,256 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 16:50:33,955 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 16:50:36,615 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 16:51:18,482 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 17:02:20,073 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 17:05:34,772 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 17:05:37,429 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 17:06:19,297 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 17:17:20,889 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 17:20:35,589 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 17:20:38,263 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 17:21:20,115 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 17:32:21,705 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 17:35:36,427 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 17:35:39,081 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 17:36:20,935 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 17:47:22,523 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 17:50:37,245 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 17:50:39,898 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 17:51:21,753 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 18:02:23,340 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 18:05:38,065 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 18:05:40,714 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 18:06:22,572 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 18:17:24,155 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 18:20:38,880 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 18:20:41,532 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

2020-10-07 18:21:23,391 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '50478'

2020-10-07 18:32:24,973 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '33685'

2020-10-07 18:35:39,698 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '59422'

2020-10-07 18:35:42,350 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '34056'

What's going on?

 

Edit to add:

Restart seems to have fixed it for now.

Edited by PeterB
Add info about restart
Link to comment
5 hours ago, PeterB said:

Edit to add:

Restart seems to have fixed it for now.

i think i see the issue, where the script to grab the port isnt exiting on openvpn restart (not container) and thus you end up with multiple processes running, i have some code i have put in place that should force a shutdown of this script if the port is not able to be assigned or openvpn process is terminated - expect to see this in the next BIG release.

Link to comment
54 minutes ago, binhex said:

guinea pig time again - wireguard support now in, if you are interested then see here:-

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=433617

 

Connected fine, first time without issue. But, I can't access the WebUI, says I've entered the wrong password. I've tried the default 'deluge' and the password I had changed this to before updating.

 

Edit: Connecting now - not sure what happened (positive I was typing it correct lol). After a couple of restarts, where one couldn't resolve www.google.com in the logs, it connected & let me get in with the PW.

Edited by xxDeadbolt
Link to comment
51 minutes ago, binhex said:

guinea pig time again - wireguard support now in, if you are interested then see here:-

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=433617

 

Works on Ubuntu 20.04 but selecting the server is ignored.  Using the below command after deleting wg0.conf (if that file exists you can't change your server it looks like)

 

docker run -d \
    --privileged \
    --cap-add=NET_ADMIN \
    -p 8112:8112 \
    -p 8118:8118 \
    -p 58846:58846 \
    -p 58946:58946 \
    --name=delugevpn \
    -v /apps/docker/deluge/data:/data \
    -v /apps/docker/deluge/config:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -v /mnt/sdb/Downloads:/home/nobody/Downloads \
    -e VPN_CLIENT=wireguard \
    -e VPN_REMOTE_SERVER=ca-montreal.privacy.network \
    -e VPN_ENABLED=yes \
    -e VPN_USER=myuser \
    -e VPN_PASS=mypass \
    -e VPN_PROV=pia \
    -e STRICT_PORT_FORWARD=yes \
    -e ENABLE_PRIVOXY=no \
    -e LAN_NETWORK=192.168.0.0/23 \
    -e NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,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 DEBUG=false \
    -e UMASK=000 \
    -e PUID=0 \
    -e PGID=0 \
    --restart unless-stopped \
    binhex/arch-delugevpn:test

Logs go like this:

 

2020-10-08 08:39:42.412235 [info] System information Linux f79174d728d3 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 GNU/Linux
2020-10-08 08:39:42.436496 [info] OS_ARCH defined as 'x86-64'                                             
2020-10-08 08:39:42.458943 [info] PUID defined as '0'                                                     
2020-10-08 08:39:43.112579 [info] PGID defined as '0'                                                     
2020-10-08 08:39:43.148871 [info] UMASK defined as '000'                                                  
2020-10-08 08:39:43.166674 [info] Permissions already set for volume mappings                             
2020-10-08 08:39:43.185016 [info] Deleting files in /tmp (non recursive)...                               
2020-10-08 08:39:43.206239 [info] VPN_ENABLED defined as 'yes'                                            
2020-10-08 08:39:43.224847 [info] VPN_CLIENT defined as 'wireguard'                                       
2020-10-08 08:39:43.242819 [info] VPN_PROV defined as 'pia'                                               
2020-10-08 08:39:43.826871 [info] VPN_CONFIG not defined (wireguard config doesnt file exists), defaulting to '/config/wireguard/wg0.conf'
2020-10-08 08:39:43.847405 [info] VPN_REMOTE_SERVER not defined (wireguard config doesnt file exists), defaulting to 'nl-amsterdam.privacy.network'
2020-10-08 08:39:43.890349 [info] VPN_REMOTE_PORT not defined (wireguard config file doesnt exists), identified port as '1337'
2020-10-08 08:39:43.906302 [info] VPN_DEVICE_TYPE defined as 'wg0'                                        
2020-10-08 08:39:43.923025 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2020-10-08 08:39:43.941149 [info] LAN_NETWORK defined as '192.168.0.0/23'             
2020-10-08 08:39:43.959089 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-10-08 08:39:43.977797 [info] VPN_USER defined as 'whatever'                                          
2020-10-08 08:39:43.996001 [info] VPN_PASS defined as 'whatever'                                        
2020-10-08 08:39:44.013963 [info] STRICT_PORT_FORWARD defined as 'yes'                                    
2020-10-08 08:39:44.031912 [info] ENABLE_PRIVOXY defined as 'no'                                          
2020-10-08 08:39:44.049843 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-10-08 08:39:44.067947 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'                               
2020-10-08 08:39:44.086106 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-10-08 08:39:44.540769 [info] Starting Supervisor...  

 

Link to comment
7 minutes ago, ratherDashing said:

Works on Ubuntu 20.04 but selecting the server is ignored.

your config is way out of date, selecting the server from env var as not been possible for over a year, see the readme here for what it now looks like:-

https://github.com/binhex/arch-delugevpn

 

if you want to change your server then edit the file /config/wireguard/wg0.conf and change the Endpoint line - note this is only possible after the first run, as the file will not exist until then.

 

Edited by binhex
  • Thanks 1
Link to comment
6 minutes ago, binhex said:

odd!, i would of liked to of seen the log for that, do you use PIA dns servers by any chance?.

Yeah, the name_servers variable hasn't been touched by me, so whatever is default. 

 

If it happens again with not being able to resolve, i'll grab a copy of the logs. 

Edited by xxDeadbolt
Link to comment
3 minutes ago, binhex said:

your config is way out of date, selecting the server from env var as not been possible for over a year, see the readme here for what it now looks like:-

https://github.com/binhex/arch-delugevpn

 

if you want to change your server then edit the file /config/wireguard/wg0.conf and change the Endpoint line.

Thanks!  I never had selecting the server as an env var before this morning, I always simply used the OpenVPN config files provided by PIA.  The "VPN_REMOTE_SERVER not defined" log line is what got me interested in fiddling with that since I didn't know how to change the server (since there are no more config files to fiddle with).  Changing the endpoint in the wg0.conf seems to have fixed it.  This is really amazing.  Thanks again!

  • Like 1
Link to comment
2 hours ago, binhex said:

guinea pig time again - wireguard support now in, if you are interested then see here:-

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=433617

 

I live in the NYC Tri-State area and switched to Montreal and the speeds are pretty amazing, way better than OpenVPN.  I have a 9th gen I3 and OpenVPN used to take ~50% a core when downloading.  I don't even see anything really running except the deluge processes now.  On my gigabit connection I am getting ~15 megabytes a second.  Amazing work.

  • Like 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.