[Support] binhex - DelugeVPN

JonathanM · February 16, 2022

16 minutes ago, tjb_altf4 said:

@DammitDaphne censor your credentials

Done. I should have seen that earlier, was too hung up on trying to cross reference paths to solve the issue.

DammitDaphne · February 16, 2022

1 hour ago, JonathanM said:

Creds were just spoof info, In the future I'll make sure to just use X's. I have tried attaching an image of the prefs about a dozen times and it will not let me upload for some reason. In preferences, the Download to: is /download, and Move completed to: is checked and set to /completed

Bob1215 · February 17, 2022

I'm hoping for some assistance setting up with custom VPN (torguard).

I'll outline the steps I have taken.

I followed the guide here (archived link) to request a port from torguard
I requested port 58846 on the Chicago server (45.128.36.154). See image in spoiler below
Spoiler
I added the conf file generated in the guide to `/config/wireguard` directory. I updated the listening port to 58846. See image in spoiler below
Spoiler
I made sure that the container was running in privileged mode per FAQ A21. See image in spoiler below

Spoiler
I changed `VPN_PROV` to "custom" and entered new torguard credentials. See image in spoiler below
Spoiler
I added a new key/value for `VPN_CLIENT` per FAQ A21. See image in spoiler below
Spoiler
I forwarded port 58846 on my router configuration page. IP 192.168.1.2 is the IP of the server running unRAID. See image in spoiler below
Spoiler
I set the incoming port to 58846 in deluge. See image in spoiler below
Spoiler
running `netstat -p` inside the container shows "58846" showing up once in the local address and once in the foreign address:

Spoiler

root@Tower:~# docker exec -it binhex-delugevpn bash
[root@d2afff8d86a1 /]# netstat -p
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 d2afff8d86a1:48947      193.32.16.148:65297     TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:55655      172.98.143.222:51918    TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:51465      172-221-146-098.r:46294 TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:33237      23-94-91-241-host:59067 TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:45075      c-174-59-92-192.h:49252 TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:8112       _gateway:46018          TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:8112       _gateway:45916          TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:53459      172.98.143.222:51918    TIME_WAIT   -                   
tcp        0      1 d2afff8d86a1:53875      45.133.6.47:63580       SYN_SENT    742/python          
tcp        0      0 localhost:58846         localhost:46090         ESTABLISHED 742/python          
tcp        0      0 d2afff8d86a1:8112       _gateway:46028          TIME_WAIT   -                   
tcp        0      0 localhost:46090         localhost:58846         ESTABLISHED 785/deluge-web      
tcp        0  25282 d2afff8d86a1:46141      198.138.1.103.unkn:8928 ESTABLISHED 742/python          
tcp        0      0 d2afff8d86a1:8112       _gateway:46024          TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:49741      pool-100-4-187-74:54644 TIME_WAIT   -                   
tcp        0 122696 d2afff8d86a1:43387      78-21-224-130.acc:36535 ESTABLISHED 742/python          
tcp        0     69 d2afff8d86a1:44259      90-224-241-130-no:46944 FIN_WAIT1   -                   
tcp        0      0 d2afff8d86a1:53263      104-188-117-156.l:40244 TIME_WAIT   -                   
tcp        0    194 d2afff8d86a1:58043      c-174-59-92-192.h:49252 FIN_WAIT1   -                   
tcp        0      0 d2afff8d86a1:50065      62.210.176.248:65424    ESTABLISHED 742/python          
tcp        0      0 d2afff8d86a1:36673      46.182.109.115:63062    TIME_WAIT   -                   
tcp        0      1 d2afff8d86a1:47417      217.138.197.77:52950    SYN_SENT    742/python          
tcp        0      0 d2afff8d86a1:54629      46.182.109.115:63062    TIME_WAIT   -                   
udp        0      0 d2afff8d86a1:51325      resolver1.privat:domain ESTABLISHED -

It can be seen the in the deluge settings screenshot that, even though I input "58846" as the "incoming port", it shows the active port as "58847". I am also see that I am considered "unconnectable" on my favorite sites. These sites show me as connecting from "45.128.36.154:58847"

Any assistance is greatly appreciated.

Edited February 17, 2022 by Bob1215
added hyperlinks to guide

DammitDaphne · February 17, 2022

18 hours ago, DammitDaphne said:

Yesterday my cache drives somehow switched to read only, and the only way I could fix it was to format and restore. Upon reinstalling deluge, the files won't download. I am connected, and all settings are the same in the container as before. I have volume mappings for /download and /completed, which again, have always worked, but now for some reason it's ignoring the mappings and trying to download to the appdata folder. I've verified the settings in the container, tried to override in the GUI preferences, and nothing seems to work. Download starts, ramps up, then slowly down and just stops.

I figured out the problem, in case anyone else ever comes across this. Prior to the issue with the flash drive, the volume mappings were set to

/download -> /mnt/cache/tdown/incomplete/
/completed -> /mnt/cache/tdown/completed/

I never had a problem with this mapping, but now it just can't function. The whole time I was feeling like it was a permissions issue, since it was acting like it was downloading then just didn't. Anyway, I was thinking about how I have the download share folder set to cache only, and hence, /mnt/cache/ seemed appropriate, but on a whim I switched it to /mnt/user/ and it immediately started downloading. All's good now.

Thanks to anyone who was looking for a solution.

strike · February 17, 2022

15 minutes ago, Bob1215 said:
I'm hoping for some assistance setting up with custom VPN (torguard).

I'll outline the steps I have taken.

I followed the guide here (archived link) to request a port from torguard

I requested port 58846 on the Chicago server (45.128.36.154). See image in spoiler below

Reveal hidden contents

I added the conf file generated in the guide to `/config/wireguard` directory. I updated the listening port to 58846. See image in spoiler below

Reveal hidden contents

I made sure that the container was running in privileged mode per FAQ A21. See image in spoiler below
Reveal hidden contents

I changed `VPN_PROV` to "custom" and entered new torguard credentials. See image in spoiler below

Reveal hidden contents

I added a new key/value for `VPN_CLIENT` per FAQ A21. See image in spoiler below

Reveal hidden contents

I forwarded port 58846 on my router configuration page. IP 192.168.1.2 is the IP of the server running unRAID. See image in spoiler below

Reveal hidden contents

I set the incoming port to 58846 in deluge. See image in spoiler below

Reveal hidden contents

running `netstat -p` inside the container shows "58846" showing up once in the local address and once in the foreign address:
Reveal hidden contents
root@Tower:~# docker exec -it binhex-delugevpn bash
[root@d2afff8d86a1 /]# netstat -p
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 d2afff8d86a1:48947      193.32.16.148:65297     TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:55655      172.98.143.222:51918    TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:51465      172-221-146-098.r:46294 TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:33237      23-94-91-241-host:59067 TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:45075      c-174-59-92-192.h:49252 TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:8112       _gateway:46018          TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:8112       _gateway:45916          TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:53459      172.98.143.222:51918    TIME_WAIT   -                   
tcp        0      1 d2afff8d86a1:53875      45.133.6.47:63580       SYN_SENT    742/python          
tcp        0      0 localhost:58846         localhost:46090         ESTABLISHED 742/python          
tcp        0      0 d2afff8d86a1:8112       _gateway:46028          TIME_WAIT   -                   
tcp        0      0 localhost:46090         localhost:58846         ESTABLISHED 785/deluge-web      
tcp        0  25282 d2afff8d86a1:46141      198.138.1.103.unkn:8928 ESTABLISHED 742/python          
tcp        0      0 d2afff8d86a1:8112       _gateway:46024          TIME_WAIT   -                   
tcp        0      0 d2afff8d86a1:49741      pool-100-4-187-74:54644 TIME_WAIT   -                   
tcp        0 122696 d2afff8d86a1:43387      78-21-224-130.acc:36535 ESTABLISHED 742/python          
tcp        0     69 d2afff8d86a1:44259      90-224-241-130-no:46944 FIN_WAIT1   -                   
tcp        0      0 d2afff8d86a1:53263      104-188-117-156.l:40244 TIME_WAIT   -                   
tcp        0    194 d2afff8d86a1:58043      c-174-59-92-192.h:49252 FIN_WAIT1   -                   
tcp        0      0 d2afff8d86a1:50065      62.210.176.248:65424    ESTABLISHED 742/python          
tcp        0      0 d2afff8d86a1:36673      46.182.109.115:63062    TIME_WAIT   -                   
tcp        0      1 d2afff8d86a1:47417      217.138.197.77:52950    SYN_SENT    742/python          
tcp        0      0 d2afff8d86a1:54629      46.182.109.115:63062    TIME_WAIT   -                   
udp        0      0 d2afff8d86a1:51325      resolver1.privat:domain ESTABLISHED -
It can be seen the in the deluge settings screenshot that, even though I input "58846" as the "incoming port", it shows the active port as "58847". I am also see that I am considered "unconnectable" on my favorite sites. These sites show me as connecting from "45.128.36.154:58847"

Any assistance is greatly appreciated.

Remove the port forwarding on your router, it's serves no purpose when you're using a vpn and is a security risk. Also request a different port from torguard and set that as the incoming port in deluge. Port 58846 is in use by the deluge deamon and I suspect that's why the active port is showing as 58847 which is the next port number in line.

Bob1215 · February 17, 2022

23 hours ago, strike said:

Remove the port forwarding on your router, it's serves no purpose when you're using a vpn and is a security risk. Also request a different port from torguard and set that as the incoming port in deluge. Port 58846 is in use by the deluge deamon and I suspect that's why the active port is showing as 58847 which is the next port number in line.

I removed the port forwarding from the router. I also requested a new port from torguard (one that is not in use by any other container) and updated the wireguard conf file "ListeningPort" parameter to this new value. I needed to make one other correction, however. Instead of using this port in the deluge network settings "Listening Port", I used the port from the torguard "manage ports" page in the column named " VPN IP" instead of the new port listed in the "Port" column of that page. I am now connectable. Thanks for the guidance, @strike.

danger781 · February 19, 2022

On 2/6/2022 at 8:31 PM, binhex said:

Q6:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thanks, my problem was the UTP settings. With that one change I've gone from 100KB/s to 20MB/s. Mad.

danger781 · February 19, 2022

I actually have another question. Previously in Transmission I was able to rename folders / torrents. I have my Media folder structure set up like:

/mnt/Media/series/MyShow/My Show Season 01/my.show.720p.hdtv.mkv

When I download a season torrent because I want to seed it, or let's say I'm missing a few episodes of a season, in Transmission I was able to:

Download the torrent as My.Show.S03.720p.hdtv.mkv.torrent
Add the torrent in a paused state with Destination: /mnt/Media/series/MyShow/
Rename the torrent to: My Show Season 01
Force Re-Check

I can't seem to find a method to to do anything similar in Deluge. I seem to be stuck with trying to download My.Show.S03.720p.hdtv.mkv.torrent which is making it difficult to fix missing episodes.

neepninja · February 21, 2022

Hi, I keep getting host error 502 when trying to reach Deluge VPN. I have my credentials text file set up with my user and password for VPN provider and also the ovpn location file in the openvpn folder. Also the template is filled out correctly. I am using cloudflare to host my dns and NGINX Proxy Manager. I have previousley been able to access deluge but not recently. ANy help would be great.

Thanks. Attatched is the error log, can proveide more if needed.

Edited February 21, 2022 by neepninja

Johns6977 · February 24, 2022

Was hoping for a guide to run two instances of DelugeVPN.

Not sure how to setup the ports and permissions. Any help would be appreciated.

takkischitt · February 28, 2022

For some reason, torrents that I delete from Deluge (both with data and without) reappear after a few minutes and start downloading again (if the data has been removed). I'm not sure what's going on. Can anyone advise?

shonen787 · March 2, 2022

Hello everyone!

I have an issue with my deluge docker container.

Haven't changed any settings in about a couple months and i'm getting the following output from my log files

Quote

Created by...
___.   .__       .__
\_ |__ |__| ____ | |__   ____ ___ ___
| __ \| |/    \| | \_/ __ \\ \/ /
| \_\ \ |   | \   Y \ ___/ >    <
|___ /__|___| /___| /\___ >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-03-01 19:41:17.513924 [info] Host is running unRAID
2022-03-01 19:41:17.528927 [info] System information Linux 246be44a2d67 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-03-01 19:41:17.545134 [info] OS_ARCH defined as 'x86-64'
2022-03-01 19:41:17.561255 [info] PUID defined as '99'
2022-03-01 19:41:17.578276 [info] PGID defined as '100'
2022-03-01 19:41:17.602339 [info] UMASK defined as '000'
2022-03-01 19:41:17.617924 [info] Permissions already set for '/config'
2022-03-01 19:41:17.634215 [info] Deleting files in /tmp (non recursive)...
2022-03-01 19:41:17.653507 [info] VPN_ENABLED defined as 'yes'
2022-03-01 19:41:17.669791 [info] VPN_CLIENT defined as 'openvpn'
2022-03-01 19:41:17.685617 [info] VPN_PROV defined as 'custom'
2022-03-01 19:41:17.705449 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/my_expressvpn_usa_-_miami_udp.ovpn
2022-03-01 19:41:17.737131 [warn] VPN configuration file /config/openvpn/my_expressvpn_usa_-_miami_udp.ovpn remote protocol is missing or malformed, assuming protocol 'udp'
2022-03-01 19:41:17.751266 [info] VPN remote server(s) defined as 'usa-miami-ca-version-2.expressnetw.com,'
2022-03-01 19:41:17.765262 [info] VPN remote port(s) defined as '1195,'
2022-03-01 19:41:17.779227 [info] VPN remote protcol(s) defined as 'udp,'
2022-03-01 19:41:17.795093 [info] VPN_DEVICE_TYPE defined as 'tun0'
2022-03-01 19:41:17.810761 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2022-03-01 19:41:17.826657 [info] LAN_NETWORK defined as '10.0.0.0/24'
2022-03-01 19:41:17.842799 [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'
2022-03-01 19:41:17.858788 [info] VPN_USER defined as 'REDACTED'
2022-03-01 19:41:17.874800 [info] VPN_PASS defined as 'REDACTED'
2022-03-01 19:41:17.890485 [info] ENABLE_PRIVOXY defined as 'no'
2022-03-01 19:41:17.908059 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-03-01 19:41:17.923902 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-03-01 19:41:17.939986 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2022-03-01 19:41:17.956072 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2022-03-01 19:41:17.972351 [info] Starting Supervisor...
2022-03-01 19:41:18,081 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-03-01 19:41:18,081 INFO Set uid to user 0 succeeded
2022-03-01 19:41:18,082 INFO supervisord started with pid 7
2022-03-01 19:41:19,084 INFO spawned: 'shutdown-script' with pid 181
2022-03-01 19:41:19,085 INFO spawned: 'start-script' with pid 182
2022-03-01 19:41:19,086 INFO spawned: 'watchdog-script' with pid 183
2022-03-01 19:41:19,086 INFO reaped unknown pid 8 (exit status 0)
2022-03-01 19:41:19,089 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2022-03-01 19:41:19,089 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-01 19:41:19,089 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-01 19:41:19,089 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-01 19:41:19,121 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2022-03-01 19:41:19,123 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2022-03-01 19:41:19,124 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2022-03-01 19:41:19,126 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-03-01 19:41:19,128 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2022-03-01 19:41:19,129 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2022-03-01 19:41:19,131 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2022-03-01 19:41:19,133 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2022-03-01 19:43:19,237 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

So i'm not quite sure what's going.
I can't access the web-ui either.
I had thought it was my pfSense ad blocker but i turned it off and i still have the same problem.
My other docker containers seem to be fine, so i'm lost.

Any help?

Tomahawk51 · March 2, 2022

Chiming in, in case there is something going on with the docker more systemically:

My DelugeVPN setup stopped working very recently (today/yesterday). I'm going through the arduous process of trying to diagnose if it's my VPN, though that is working fine on the client app. I'll keep checking here to see if others are having issues (and fined a solution).

binhex · March 2, 2022

11 hours ago, shonen787 said:

Hello everyone!

I have an issue with my deluge docker container.
Haven't changed any settings in about a couple months and i'm getting the following output from my log files

Quote

Created by...
___.   .__       .__
\_ |__ |__| ____ | |__   ____ ___ ___
| __ \| |/    \| | \_/ __ \\ \/ /
| \_\ \ |   | \   Y \ ___/ >    |___ /__|___| /___| /\___ >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/
2022-03-01 19:41:17.513924 [info] Host is running unRAID
2022-03-01 19:41:17.528927 [info] System information Linux 246be44a2d67 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-03-01 19:41:17.545134 [info] OS_ARCH defined as 'x86-64'
2022-03-01 19:41:17.561255 [info] PUID defined as '99'
2022-03-01 19:41:17.578276 [info] PGID defined as '100'
2022-03-01 19:41:17.602339 [info] UMASK defined as '000'
2022-03-01 19:41:17.617924 [info] Permissions already set for '/config'
2022-03-01 19:41:17.634215 [info] Deleting files in /tmp (non recursive)...
2022-03-01 19:41:17.653507 [info] VPN_ENABLED defined as 'yes'
2022-03-01 19:41:17.669791 [info] VPN_CLIENT defined as 'openvpn'
2022-03-01 19:41:17.685617 [info] VPN_PROV defined as 'custom'
2022-03-01 19:41:17.705449 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/my_expressvpn_usa_-_miami_udp.ovpn
2022-03-01 19:41:17.737131 [warn] VPN configuration file /config/openvpn/my_expressvpn_usa_-_miami_udp.ovpn remote protocol is missing or malformed, assuming protocol 'udp'
2022-03-01 19:41:17.751266 [info] VPN remote server(s) defined as 'usa-miami-ca-version-2.expressnetw.com,'
2022-03-01 19:41:17.765262 [info] VPN remote port(s) defined as '1195,'
2022-03-01 19:41:17.779227 [info] VPN remote protcol(s) defined as 'udp,'
2022-03-01 19:41:17.795093 [info] VPN_DEVICE_TYPE defined as 'tun0'
2022-03-01 19:41:17.810761 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2022-03-01 19:41:17.826657 [info] LAN_NETWORK defined as '10.0.0.0/24'
2022-03-01 19:41:17.842799 [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'
2022-03-01 19:41:17.858788 [info] VPN_USER defined as 'REDACTED'
2022-03-01 19:41:17.874800 [info] VPN_PASS defined as 'REDACTED'
2022-03-01 19:41:17.890485 [info] ENABLE_PRIVOXY defined as 'no'
2022-03-01 19:41:17.908059 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-03-01 19:41:17.923902 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-03-01 19:41:17.939986 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2022-03-01 19:41:17.956072 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2022-03-01 19:41:17.972351 [info] Starting Supervisor...
2022-03-01 19:41:18,081 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-03-01 19:41:18,081 INFO Set uid to user 0 succeeded
2022-03-01 19:41:18,082 INFO supervisord started with pid 7
2022-03-01 19:41:19,084 INFO spawned: 'shutdown-script' with pid 181
2022-03-01 19:41:19,085 INFO spawned: 'start-script' with pid 182
2022-03-01 19:41:19,086 INFO spawned: 'watchdog-script' with pid 183
2022-03-01 19:41:19,086 INFO reaped unknown pid 8 (exit status 0)
2022-03-01 19:41:19,089 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
2022-03-01 19:41:19,089 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-01 19:41:19,089 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-01 19:41:19,089 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-01 19:41:19,121 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf
2022-03-01 19:41:19,123 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf
2022-03-01 19:41:19,124 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf
2022-03-01 19:41:19,126 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf
2022-03-01 19:41:19,128 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf
2022-03-01 19:41:19,129 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf
2022-03-01 19:41:19,131 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf
2022-03-01 19:41:19,133 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf
2022-03-01 19:43:19,237 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

Quote

So i'm not quite sure what's going.
I can't access the web-ui either.
I had thought it was my pfSense ad blocker but i turned it off and i still have the same problem.
My other docker containers seem to be fine, so i'm lost.
Any help?

Something is preventing DNS lookup on your LAN, recheck pfsense, pi hole etc, also you might want to remove the PIA name servers, they are very unreliable recently, so change NAME_SERVERS to have a value of:-

84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

Sent from my CLT-L09 using Tapatalk

binhex · March 2, 2022

10 hours ago, Tomahawk51 said:

Chiming in, in case there is something going on with the docker more systemically:

My DelugeVPN setup stopped working very recently (today/yesterday). I'm going through the arduous process of trying to diagnose if it's my VPN, though that is working fine on the client app. I'll keep checking here to see if others are having issues (and fined a solution).

please dont generalise, what might look like everybody has the same problem (cant access web ui) there are literally dozens of reasons for this, please do the following to help identify the problem:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

shonen787 · March 2, 2022

5 hours ago, binhex said:
Something is preventing DNS lookup on your LAN, recheck pfsense, pi hole etc, also you might want to remove the PIA name servers, they are very unreliable recently, so change NAME_SERVERS to have a value of:-
84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
Sent from my CLT-L09 using Tapatalk

So i did try checking if it was a DNS issue on my LAN. Everything seems to be working fine. I've also tried from other docker containers to see if i can resolve domain names and it works fine.

I'm really only having issues with any repo pertaining to Binhex.

I'll keep chugging along and if i get anywhere i guess i'll post an update.

binhex · March 2, 2022

21 minutes ago, shonen787 said:

So i did try checking if it was a DNS issue on my LAN. Everything seems to be working fine. I've also tried from other docker containers to see if i can resolve domain names and it works fine.

I'm really only having issues with any repo pertaining to Binhex.

I'll keep chugging along and if i get anywhere i guess i'll post an update.

did you try this?

5 hours ago, binhex said:
also you might want to remove the PIA name servers, they are very unreliable recently, so change NAME_SERVERS to have a value of:-
84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

shonen787 · March 2, 2022

9 minutes ago, binhex said:

did you try this?

Yup. One of the first things i tried.

So much so that i slapped those dns servers straight into my pfSense.

JonathanM · March 2, 2022

43 minutes ago, binhex said:
change NAME_SERVERS to have a value of:-
84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

That's got nothing to do with your LAN environment.

Messing with your pfSense won't do anything inside the VPN tunnel.

Have you changed the NAME_SERVERS value as asked?

shonen787 · March 2, 2022

1 hour ago, JonathanM said:

That's got nothing to do with your LAN environment.

Messing with your pfSense won't do anything inside the VPN tunnel.

Have you changed the NAME_SERVERS value as asked?

Yes i did, here are the screenshots from the unraid setting and the log.

Edit: Would this be the problem?

image.png.40e92e6b069c55a543373a3f9533b88d.png

It seems that something is adding a comma to the vpn_remote_server but i'm not sure what.

Edit Edit: Ignore that last edit, i'm dumb... >.>

Edited March 2, 2022 by shonen787

gh0stkey · March 2, 2022

Hi guys,

Recently I rebooted my server and everything but the Web UI is working. I haven't tweaked or changed anything, I'm using PIA and wireguard as my protocol. Deluge seems to be running as I tested the connection using Radarr/Sonarr but the Web UI takes too long to respond... I'm using 192.168.x.x:8112 for the Web UI. Here are the logs:

----

Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2022-03-02 10:57:32.372459 [info] Host is running unRAID
2022-03-02 10:57:32.389001 [info] System information Linux 1186b3476721 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-03-02 10:57:32.409198 [info] OS_ARCH defined as 'x86-64'
2022-03-02 10:57:32.428556 [info] PUID defined as '99'
2022-03-02 10:57:32.450742 [info] PGID defined as '100'
2022-03-02 10:57:32.518203 [info] UMASK defined as '000'
2022-03-02 10:57:32.535265 [info] Permissions already set for '/config'
2022-03-02 10:57:32.553728 [info] Deleting files in /tmp (non recursive)...
2022-03-02 10:57:32.578908 [info] VPN_ENABLED defined as 'yes'
2022-03-02 10:57:32.597521 [info] VPN_CLIENT defined as 'wireguard'
2022-03-02 10:57:32.615679 [info] VPN_PROV defined as 'pia'
2022-03-02 10:57:32.774009 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2022-03-02 10:57:32.803786 [info] VPN_REMOTE_SERVER defined as 'nl-amsterdam.privacy.network'
2022-03-02 10:57:32.841075 [info] VPN_REMOTE_PORT defined as '1337'
2022-03-02 10:57:32.857614 [info] VPN_DEVICE_TYPE defined as 'wg0'
2022-03-02 10:57:32.873911 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2022-03-02 10:57:32.892720 [info] LAN_NETWORK defined as '192.168.1.0/24'
2022-03-02 10:57:32.912978 [info] NAME_SERVERS defined as '1.1.1.1'
2022-03-02 10:57:32.935136 [info] VPN_USER defined as 'xxxxxxx'
2022-03-02 10:57:32.953630 [info] VPN_PASS defined as 'xxxxxxxx'
2022-03-02 10:57:32.972099 [info] STRICT_PORT_FORWARD defined as 'no'
2022-03-02 10:57:32.990158 [info] ENABLE_PRIVOXY defined as 'no'
2022-03-02 10:57:33.012435 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-03-02 10:57:33.032597 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-03-02 10:57:33.052363 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2022-03-02 10:57:33.072121 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2022-03-02 10:57:33.092599 [info] Starting Supervisor...
2022-03-02 10:57:33,203 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-03-02 10:57:33,203 INFO Set uid to user 0 succeeded
2022-03-02 10:57:33,205 INFO supervisord started with pid 7
2022-03-02 10:57:34,208 INFO spawned: 'shutdown-script' with pid 161
2022-03-02 10:57:34,210 INFO spawned: 'start-script' with pid 162
2022-03-02 10:57:34,212 INFO spawned: 'watchdog-script' with pid 163
2022-03-02 10:57:34,212 INFO reaped unknown pid 8 (exit status 0)
2022-03-02 10:57:34,216 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2022-03-02 10:57:34,216 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-02 10:57:34,216 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-02 10:57:34,217 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-02 10:57:34,219 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-03-02 10:57:34,390 DEBG 'start-script' stdout output:
[info] Token generated for PIA wireguard authentication

2022-03-02 10:57:34,410 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...

2022-03-02 10:57:34,784 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2022-03-02 10:57:34,797 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2022-03-02 10:57:34,801 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2022-03-02 10:57:34,801 DEBG 'start-script' stdout output:
[info] ip route defined as follows...

2022-03-02 10:57:34,802 DEBG 'start-script' stdout output:
--------------------

2022-03-02 10:57:34,803 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.8
192.168.1.0/24 via 172.17.0.1 dev eth0
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1

2022-03-02 10:57:34,803 DEBG 'start-script' stdout output:
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.8
local 172.17.0.8 dev eth0 table local proto kernel scope host src 172.17.0.8
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.8
--------------------

2022-03-02 10:57:34,807 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 28672 8 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables 28672 18 ip6table_filter,xt_conntrack,iptable_filter,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2022-03-02 10:57:34,807 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2022-03-02 10:57:34,856 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2022-03-02 10:57:34,857 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 195.78.54.108/32 -i eth0 -j ACCEPT
-A INPUT -s 212.102.34.144/32 -i eth0 -j ACCEPT
-A INPUT -s 212.102.35.145/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 195.78.54.108/32 -o eth0 -j ACCEPT
-A OUTPUT -d 212.102.34.144/32 -o eth0 -j ACCEPT
-A OUTPUT -d 212.102.35.145/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2022-03-02 10:57:34,858 DEBG 'start-script' stdout output:
--------------------

2022-03-02 10:57:34,861 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-03-02 10:57:34,870 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-03-02 10:57:34,876 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-03-02 10:57:34,877 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-03-02 10:57:34,887 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.51.190.229 dev wg0

2022-03-02 10:57:34,893 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2022-03-02 10:57:34,912 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2022-03-02 10:57:34,913 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2022-03-02 10:57:34,914 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2022-03-02 10:57:34,915 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2022-03-02 10:57:34,918 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2022-03-02 10:57:34,919 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2022-03-02 10:57:34,921 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2022-03-02 10:57:36,102 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2022-03-02 10:57:36,393 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 195.78.54.108

2022-03-02 10:57:36,393 DEBG 'start-script' stdout output:
[info] Port forwarding is not enabled

2022-03-02 10:57:36,394 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2022-03-02 10:57:37,046 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.51.190.229 different, marking for reconfigure

2022-03-02 10:57:37,048 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-03-02 10:57:37,051 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2022-03-02 10:57:37,052 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-03-02 10:57:37,281 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.51.249.86'
[info] Deluge key 'listen_interface' will have a new value '10.51.190.229'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-03-02 10:57:37,401 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-03-02 10:57:37,507 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of xxxxxxxxxxxxxxxxxxxxxxx'
[info] Deluge key 'default_daemon' will have a new value 'xxxxxxxxxxxxxxxxxxxxxxxxxxx'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-03-02 10:57:37,736 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-03-02 10:57:37,847 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-03-02 10:57:39,650 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2022-03-02 10:57:41,436 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (6890, 6890)
Configuration value successfully updated.

2022-03-02 10:57:43,314 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-03-02 10:57:43,314 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-03-02 10:57:43,314 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

binhex · March 2, 2022

43 minutes ago, gh0stkey said:

I'm using 192.168.x.x:8112

that log shows a successful start, is the ip of the machine running the web browser in the 192.168.1.x range?.

binhex · March 2, 2022

5 hours ago, shonen787 said:

Yes i did, here are the screenshots from the unraid setting and the log.

Edit: Would this be the problem?

It seems that something is adding a comma to the vpn_remote_server but i'm not sure what.

Edit Edit: Ignore that last edit, i'm dumb... >.>

well you can def see the dns resolution failure in your screenshot above, to confirm left click deluge icon and select 'console' then type 'ping www.google.com' and that should failto resolve, now the question is what on your lan is blocking it.

gh0stkey · March 2, 2022

Hi Binhex,

Yes it is running on 192.168.1.5.

binhex · March 2, 2022

13 minutes ago, gh0stkey said:

Hi Binhex,

Yes it is running on 192.168.1.5.

ok try accessing web ui from another machine/device, try different browser too, also just to double check the network type for the container should be set to 'bridge' is this the case?.

[Support] binhex - DelugeVPN

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Ryanoc3ros

Dad_Rage

binhex

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation