Jump to content

[Support] binhex - DelugeVPN

binhex

By binhex
in Docker Containers

Recommended Posts

Recommended

Posted by binhex,

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A new image has now been rolled out for all vpn enabled docker images (25th Feb 2021) i produce with the fix in place, i would encourage everyone to update to the recently created 'latest' tagged image.   You can force the upgrade by toggling 'basic view' to 'advanced view' and then clicking on
Recommended by binhex
  • Thanks
  • Like

8 reactions

Go to this post
Recommended

Posted by Ryanoc3ros,

Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead. You can find your service credentials by following these steps: Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/ Click on the NordVPN tab on the left panel which is under the Services tab.

NordVPN authentication issues - Solution

Recommended by binhex

  • Upvote
  • Thanks
  • Like

13 reactions

Go to this post
clusterbox Noob

clusterbox

Posted
Posted

I'm running the latest container and receiving 12 looped errors stating:

  

2024-07-06 00:31:17,928 DEBG 'start-script' stdout output:

[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

[info] 6 retries left

[info] Retrying in 10 secs...

 

Redacted Docker logs are attached.   Haven't made any major changes on my end in months.  Any ideas?  

delugevpn_docker_logs.rtf

Link to comment
  • Replies 10.5k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Ryanoc3ros
Ryanoc3ros

Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to u

Dad_Rage
Dad_Rage

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

binhex
binhex

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

Posted Images

Duggie264 Rookie

Duggie264

Posted
Posted
On 7/2/2024 at 9:57 PM, Duggie264 said:

Hi, I have just updated my container, and I have lost connection to it  (Authentication Failed) from oher containers.

It seems to start and run OK, however all the preferences are blank, and if I fill them in and click apply/save, they are blank again when I re-open preferences.

I have downgraded, but the issue perists. I have updated back to lates and issue perisists.

Any idea?

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

2024-07-02 21:48:04.780385 [info] Host is running unRAID
2024-07-02 21:48:04.809344 [info] System information Linux 8a9f79087f80 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
2024-07-02 21:48:04.849722 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-02 21:48:04.885921 [info] PUID defined as '99'
2024-07-02 21:48:04.928030 [info] PGID defined as '100'
2024-07-02 21:48:04.995172 [info] UMASK defined as '000'
2024-07-02 21:48:05.032635 [info] Permissions already set for '/config'
2024-07-02 21:48:05.072638 [info] Deleting files in /tmp (non recursive)...
2024-07-02 21:48:05.132992 [info] VPN_ENABLED defined as 'yes'
2024-07-02 21:48:05.175084 [info] VPN_CLIENT defined as 'openvpn'
2024-07-02 21:48:05.214735 [info] VPN_PROV defined as 'custom'
2024-07-02 21:48:05.259379 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/privado.ams-025.udp.1194.ovpn
2024-07-02 21:48:05.360141 [info] VPN remote server(s) defined as 'ams-025.vpn.privado.io,'
2024-07-02 21:48:05.391894 [info] VPN remote port(s) defined as '1194,'
2024-07-02 21:48:05.428314 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-02 21:48:05.467626 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-02 21:48:05.505366 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-02 21:48:05.544037 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2024-07-02 21:48:11.078408 [info] LAN_NETWORK defined as '192.168.1.0/24'
2024-07-02 21:48:11.138617 [info] LAN_NETWORK exported as '192.168.1.0/24'
2024-07-02 21:48:11.176417 [info] VPN_USER defined as 'yeah you dont need to know this'
2024-07-02 21:48:11.215889 [info] VPN_PASS defined as 'or this'
2024-07-02 21:48:11.261060 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-07-02 21:48:11.300181 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-07-02 21:48:11.337989 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2024-07-02 21:48:11.382047 [info] ENABLE_SOCKS defined as 'no'
2024-07-02 21:48:11.423863 [info] ENABLE_PRIVOXY defined as 'no'
2024-07-02 21:48:11.462392 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2024-07-02 21:48:11.501404 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2024-07-02 21:48:11.540861 [info] DELUGE_ENABLE_WEBUI_PASSWORD defined as 'yes'
2024-07-02 21:48:11.582641 [info] Starting Supervisor...
2024-07-02 21:48:11,822 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2024-07-02 21:48:11,822 INFO Set uid to user 0 succeeded
2024-07-02 21:48:11,825 INFO supervisord started with pid 7
2024-07-02 21:48:12,829 INFO spawned: 'start-script' with pid 294
2024-07-02 21:48:12,832 INFO spawned: 'watchdog-script' with pid 295
2024-07-02 21:48:12,832 INFO reaped unknown pid 8 (exit status 0)
2024-07-02 21:48:12,840 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-07-02 21:48:12,840 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-02 21:48:12,840 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-02 21:48:13,244 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via adapter eth0

2024-07-02 21:48:13,247 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-07-02 21:48:13,249 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.10 
192.168.1.0/24 via 172.17.0.1 dev eth0 
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 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
local 172.17.0.10 dev eth0 table local proto kernel scope host src 172.17.0.10 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.10 

2024-07-02 21:48:13,250 DEBG 'start-script' stdout output:
--------------------

2024-07-02 21:48:13,258 DEBG 'start-script' stdout output:
iptable_mangle         16384  0
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  12 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_nat,ip6_tables,ip_tables,iptable_nat,xt_MASQUERADE,iptable_mangle,xt_mark

2024-07-02 21:48:13,258 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2024-07-02 21:48:13,379 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-07-02 21:48:13,382 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s correct Public IP/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s correct Public IP/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 tun0 -j ACCEPT
-A OUTPUT -d correct Public IP/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d correct Public IP/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 tun0 -j ACCEPT

2024-07-02 21:48:13,385 DEBG 'start-script' stdout output:
--------------------

2024-07-02 21:48:13,387 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-07-02 21:48:13,399 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 Note: --data-ciphers-fallback with cipher 'AES-256-CBC' disables data channel offload.
2024-07-02 21:48:13 OpenVPN 2.6.11 [git:makepkg/ddf6bf6d2a135835+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 20 2024
2024-07-02 21:48:13 library versions: OpenSSL 3.3.1 4 Jun 2024, LZO 2.10

2024-07-02 21:48:13,400 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 DCO version: N/A

2024-07-02 21:48:13,400 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-07-02 21:48:13,401 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 TCP/UDP: Preserving recently used remote address: [AF_INET]correct Public IP:1194
2024-07-02 21:48:13 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-07-02 21:48:13 UDPv4 link local: (not bound)
2024-07-02 21:48:13 UDPv4 link remote: [AF_INET]correct Public IP:1194

2024-07-02 21:48:13,419 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 TLS: Initial packet from [AF_INET]correct Public IP:1194, sid=92d6a28f f5ca694f

2024-07-02 21:48:13,489 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 VERIFY OK: depth=1, CN=Privado

2024-07-02 21:48:13,489 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 VERIFY KU OK
2024-07-02 21:48:13 Validating certificate extended key usage
2024-07-02 21:48:13 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-07-02 21:48:13 VERIFY EKU OK
2024-07-02 21:48:13 VERIFY OK: depth=0, CN=ams-025.vpn.privado.io

2024-07-02 21:48:13,650 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 Control Channel: TLSv1.2, cipher SSLv3 DHE-RSA-AES256-SHA, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 4096 bits DH
2024-07-02 21:48:13 [ams-025.vpn.privado.io] Peer Connection Initiated with [AF_INET]correct Public IP:1194
2024-07-02 21:48:13 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1

2024-07-02 21:48:13,651 DEBG 'start-script' stdout output:
2024-07-02 21:48:13 TLS: tls_multi_process: initial untrusted session promoted to trusted

2024-07-02 21:48:14,903 DEBG 'start-script' stdout output:
2024-07-02 21:48:14 SENT CONTROL [ams-025.vpn.privado.io]: 'PUSH_REQUEST' (status=1)

2024-07-02 21:48:14,918 DEBG 'start-script' stdout output:
2024-07-02 21:48:14 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 493216,sndbuf 493216,explicit-exit-notify 5,route-gateway 172.21.46.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.21.46.194 255.255.254.0,peer-id 13'
2024-07-02 21:48:14 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified

2024-07-02 21:48:14,919 DEBG 'start-script' stdout output:
2024-07-02 21:48:14 Socket Buffers: R=[212992->986432] S=[212992->986432]
2024-07-02 21:48:14 OPTIONS IMPORT: --ifconfig/up options modified
2024-07-02 21:48:14 OPTIONS IMPORT: route options modified
2024-07-02 21:48:14 OPTIONS IMPORT: route-related options modified
2024-07-02 21:48:14 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2024-07-02 21:48:14 Using peer cipher 'AES-256-CBC'
2024-07-02 21:48:14 net_route_v4_best_gw query: dst 0.0.0.0
2024-07-02 21:48:14 net_route_v4_best_gw result: via 172.17.0.1 dev eth0
2024-07-02 21:48:14 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:0a

2024-07-02 21:48:14,919 DEBG 'start-script' stdout output:
2024-07-02 21:48:14 TUN/TAP device tun0 opened
2024-07-02 21:48:14 net_iface_mtu_set: mtu 1500 for tun0

2024-07-02 21:48:14,919 DEBG 'start-script' stdout output:
2024-07-02 21:48:14 net_iface_up: set tun0 up
2024-07-02 21:48:14 net_addr_v4_add: 172.21.46.194/23 dev tun0
2024-07-02 21:48:14 /root/openvpnup.sh tun0 1500 0 172.21.46.194 255.255.254.0 init

2024-07-02 21:48:14,927 DEBG 'start-script' stdout output:
2024-07-02 21:48:14 Data Channel: cipher 'AES-256-CBC', auth 'SHA256', peer-id: 13
2024-07-02 21:48:14 Timers: ping 20, ping-restart 40
2024-07-02 21:48:14 Protocol options: explicit-exit-notify 5

2024-07-02 21:48:18,182 DEBG 'start-script' stdout output:
2024-07-02 21:48:18 net_route_v4_add: correct Public IP/32 via 172.17.0.1 dev [NULL] table 0 metric -1

2024-07-02 21:48:18,182 DEBG 'start-script' stdout output:
2024-07-02 21:48:18 net_route_v4_add: 0.0.0.0/1 via 172.21.46.1 dev [NULL] table 0 metric -1
2024-07-02 21:48:18 net_route_v4_add: 128.0.0.0/1 via 172.21.46.1 dev [NULL] table 0 metric -1
2024-07-02 21:48:18 net_route_v4_add: 0.0.0.0/0 via 172.21.46.1 dev [NULL] table 0 metric -1
2024-07-02 21:48:18 Initialization Sequence Completed

2024-07-02 21:48:21,038 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2024-07-02 21:48:21,178 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address correct Public IP.10

2024-07-02 21:48:21,179 DEBG 'start-script' stdout output:
[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

2024-07-02 21:48:21,214 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 172.21.46.194 different, marking for reconfigure

2024-07-02 21:48:21,222 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2024-07-02 21:48:21,228 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2024-07-02 21:48:21,232 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2024-07-02 21:48:21,651 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '172.21.32.153'
[info] Deluge key 'listen_interface' will have a new value '172.21.46.194'
[info] Writing changes to Deluge config file '/config/core.conf'...

2024-07-02 21:48:21,978 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2024-07-02 21:48:22,260 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '59ca9119f156488fba9c7a3ee7ad56cd'
[info] Deluge key 'default_daemon' will have a new value '59ca9119f156488fba9c7a3ee7ad56cd'
[info] Writing changes to Deluge config file '/config/web.conf'...

2024-07-02 21:48:22,315 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2024-07-02 21:48:22,786 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2024-07-02 21:48:25,457 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14f0f21704d0 current result: None>

2024-07-02 21:48:25,564 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2024-07-02 21:48:25,565 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2024-07-02 21:48:25,565 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

image.png.320573addec5eea368a219a983c1a3b0.png

Any Ideas?

So, depite this being a recent rebuild  (had a struggle resolving some VPN issues) and working without fault for over a week before thsi issue manifested (immediatly post an update) I could not find the problem, however managed to reoslve the symptoms by completely erasing the appdata folders and images, and rebuilding from scratch.

Link to comment
craigr Collaborator

craigr

Posted
Posted

binhex I just updated today again to your newest.  I have never started deluge and had it come online so quickly.  It only took a few moments to get the web GUI and thinclient up.  Did you speed things up somehow?

 

Thanks!

Link to comment
bigbangus Contributor

bigbangus

Posted
Posted
On 6/29/2024 at 5:53 AM, binhex said:

So how to prevent this situation - I will put in additional code to drop all packets but permit name resolution for a short period of time on start-up (will be included in the next image), this will allow name resolution of the endpoint but will ensure all other traffic is not permitted, even if name resolution fails, as was your case.

 

[...]

UPDATE - Image now built with change included above, please do note there are a number of additional changes included unrelated to the above.

 

Thank you! 

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
18 hours ago, craigr said:

binhex I just updated today again to your newest.  I have never started deluge and had it come online so quickly.  It only took a few moments to get the web GUI and thinclient up.  Did you speed things up somehow?

 

Thanks!

This maybe due to the fact you were targeting slow name servers, i did notice the 'DNS Watch' name servers  (84.200.xx.xx) present a 10-15 second delay in start up time, switch to cloudflare and startup was vastly improved, so perhaps you have switched name servers around, or perhaps DNS Watch has improved performance on their name servers - fear not though, if you can access the web ui of the application then the tunnel is established and all required iptables rules are in place.

  • Thanks 1
Link to comment
gizmo000 Noob

gizmo000

Posted
Posted
On 7/6/2024 at 12:46 AM, clusterbox said:

I'm running the latest container and receiving 12 looped errors stating:

  

2024-07-06 00:31:17,928 DEBG 'start-script' stdout output:

[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

[info] 6 retries left

[info] Retrying in 10 secs...

 

Redacted Docker logs are attached.   Haven't made any major changes on my end in months.  Any ideas?  

delugevpn_docker_logs.rtf 21.59 kB · 1 download

 

I am also experiencing these json errors in binhex-qbittorrentvpn ... however, in binhex-delugevpn I'm getting different errors:

  

2024-07-11 12:35:01,787 DEBG 'start-script' stdout output:
2024-07-11 12:35:01 [montreal411] Peer Connection Initiated with [AF_INET]199.36.*.*:1198

2024-07-11 12:35:02,957 DEBG 'start-script' stdout output:
2024-07-11 12:35:02 AUTH: Received control message: AUTH_FAILED
2024-07-11 12:35:02 SIGTERM[soft,auth-failure] received, process exiting

2024-07-11 12:35:02,962 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-07-11 12:35:02,977 DEBG 'start-script' stdout output:
2024-07-11 12:35:02 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 

2024-07-11 12:35:02,977 DEBG 'start-script' stdout output:
2024-07-11 12:35:02 WARNING: file 'credentials.conf' is group or others accessible
2024-07-11 12:35:02 OpenVPN 2.6.11 [git:makepkg/ddf6bf6d2a135835+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 20 2024
2024-07-11 12:35:02 library versions: OpenSSL 3.3.1 4 Jun 2024, LZO 2.10
2024-07-11 12:35:02 DCO version: N/A

2024-07-11 12:35:02,978 DEBG 'start-script' stdout output:
2024-07-11 12:35:02 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-07-11 12:35:02,980 DEBG 'start-script' stdout output:
2024-07-11 12:35:02 TCP/UDP: Preserving recently used remote address: [AF_INET]104.18.*.*:1198
2024-07-11 12:35:02 UDPv4 link local: (not bound)
2024-07-11 12:35:02 UDPv4 link remote: [AF_INET]104.18.*.*:1198

2024-07-11 12:36:02,278 DEBG 'start-script' stdout output:
2024-07-11 12:36:02 [UNDEF] Inactivity timeout (--ping-restart), restarting

2024-07-11 12:36:02,279 DEBG 'start-script' stdout output:
2024-07-11 12:36:02 SIGHUP[soft,ping-restart] received, process restarting

2024-07-11 12:36:02,280 DEBG 'start-script' stdout output:
2024-07-11 12:36:02 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

 

These only started popping up after the container update, which had been working for months with no issue.

 

I haven't been able to get this deluge container to connect to wireguard in months ... I gave up and switched to OpenVPN, but now OpenVPN isn't connecting either :(

 

If you need more diagnostics please let me know and I'll post them.  

 

I'm on UnRaid 6.12.6.

Link to comment
gizmo000 Noob

gizmo000

Posted
Posted
5 hours ago, binhex said:

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

binhex I am embarrassed beyond belief so I will own up to my mistake ... my PIA subscription had expired.

 

For anyone reading this, I also had excess wireguard conf files in my /config directory which was throwing things off as well.

 

I removed the extra conf files, updated my subscription, and I'm back up on wireguard with the most recent versions.

 

binhex please PM me some way that so I can buy you a beer or three ... seriously I am embarrassed.

  • Like 1
Link to comment
gizmo000 Noob

gizmo000

Posted
Posted (edited)
7 minutes ago, JonathanM said:

I'll pile on a little. First post of this thread.

 

This is a good reminder ... however, I get "authorization failed" to a gmail address that I won't re-post here for privacy reasons.

  

Sorry, we weren't able to complete your payment at this time. Please try again later.
If you continue to encounter problems, please contact customer service.

 

Edit:

If I send money without using the link through PayPal's site, it completes successfully.  Hopefully his email hasn't changed! XDXD

Edited by gizmo000
Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
6 hours ago, gizmo000 said:

This is a good reminder ... however, I get "authorization failed" to a gmail address that I won't re-post here for privacy reasons.

  

Sorry, we weren't able to complete your payment at this time. Please try again later.
If you continue to encounter problems, please contact customer service.

 

Edit:

If I send money without using the link through PayPal's site, it completes successfully.  Hopefully his email hasn't changed! XDXD

All good I got the donation, thank you.

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
14 minutes ago, gizmo000 said:

@binhex it may also be worth adding to A17 to check that the VPN subscription is active, since that's exactly the situation I encountered...just an idea.

 

Thanks again for putting up with us plebes...

Done.

Link to comment
nurollinsiii41 Noob

nurollinsiii41

Posted
Posted (edited)

I'm at a loss. I'm not sure where to go. Deluge appears to be up w/ a IP via PIA. But I can't hit the WebUI, nor can I sent a torrent to it, it fails immediately. This happened out of nowhere so I'm not sure what has changed. Any help would be appreciated.



**UPDATE** 

it worked for a few min, i turned off debugging, and it stopped working again.

 

logs.txt

Edited by nurollinsiii41
Link to comment
anibis2 Rookie

anibis2

Posted
Posted (edited)

I'm having an issue on Unraid 7.0 b2 where FlareSolverr stops working after the 7.0 b1 > b2 OS update. I had no issues when updating from the previous version to 7.0 b1. I've upgraded and downgraded a few times, and the issue is definitely related to the patch. Prowlarr is also routed the same way but works fine. I've tried the two different FlareSolverr dockers, both had the same behavior. FlareSolverr does work when I pull it out of the DelugeVPN docker network. I am routing the two containers by setting their networks to none and adding a string pointing to DelugeVPN in the Extra Parameters field. The WebUI on FlareSolver does come up after about 5 minutes (usually takes seconds), it loads normally thereafter. Sonarr/Radarr/Prowlarr are unable to communicate with FlareSolverr. When I run a test I see a hit come in the logs, but it doesn't get a response. The logs look fine otherwise, no errors or anything. 

 

 

 

 

Edited by anibis2
Link to comment
craigr Collaborator

craigr

Posted
Posted
On 7/8/2024 at 10:19 AM, binhex said:

This maybe due to the fact you were targeting slow name servers, i did notice the 'DNS Watch' name servers  (84.200.xx.xx) present a 10-15 second delay in start up time, switch to cloudflare and startup was vastly improved, so perhaps you have switched name servers around, or perhaps DNS Watch has improved performance on their name servers - fear not though, if you can access the web ui of the application then the tunnel is established and all required iptables rules are in place.

No fear here.  Just extra happy that the startup time is faster.

 

Thanks again!

  • Like 1
Link to comment
Smith007 Noob

Smith007

Posted
Posted
On 7/30/2020 at 2:03 AM, 1q8448q1 said:

I found the solution. The VPN provider gives out different credentials escpecially for every ovpn config you create. And hides them! Very bad user interface. Oh my. Problem solved. Thank you!

Hi - I'm facing the same issue. Where can I find those different (per ovpn config) credentials?

Link to comment
craigr Collaborator

craigr

Posted
Posted

Hey binhex, I woke up to deluge down.  A restart fixed it, but looking at the log... "[info] Successfully assigned and bound incoming port '29732'" every ten minutes, but when I shut down (many times):

  

2024-07-23 10:36:34,682 INFO waiting for start-script, watchdog-script to die
2024-07-23 10:36:35,183 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:35,684 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:36,186 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:36,687 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:37,188 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

  

2024-07-23 09:27:58,158 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 09:37:58,306 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 09:47:58,461 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 09:57:58,623 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 10:07:58,796 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 10:17:58,965 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 10:27:59,142 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '29732'

2024-07-23 10:36:28,664 INFO reaped unknown pid 56 (terminated by SIGTERM)
2024-07-23 10:36:28,664 WARN received SIGTERM indicating exit request
2024-07-23 10:36:28,664 DEBG killing watchdog-script (pid 392) with signal SIGTERM
2024-07-23 10:36:28,664 INFO waiting for start-script, watchdog-script to die
2024-07-23 10:36:28,665 DEBG 'watchdog-script' stdout output:
[info] Waiting for child processes to exit...

2024-07-23 10:36:28,665 DEBG received SIGCHLD indicating a child quit
2024-07-23 10:36:29,167 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781
837' still running, waiting...

2024-07-23 10:36:29,669 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:30,170 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:30,671 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:31,173 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:31,674 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:31,674 INFO waiting for start-script, watchdog-script to die
2024-07-23 10:36:32,175 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:32,677 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:33,178 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:33,679 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:34,181 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:34,682 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:34,682 INFO waiting for start-script, watchdog-script to die
2024-07-23 10:36:35,183 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:35,684 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:36,186 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:36,687 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:37,188 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:37,689 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

2024-07-23 10:36:37,690 INFO waiting for start-script, watchdog-script to die
2024-07-23 10:36:38,191 DEBG 'watchdog-script' stdout output:
[info] Child process with pid id '781' still running, waiting...

 

Link to comment
craigr Collaborator

craigr

Posted
Posted

Spoke too soon.  This is with zero changes:

  

2024-07-23 10:37:24,532 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2024-07-23 10:46:59,289 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23881'

2024-07-23 10:56:59,444 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23881'

 

Every ten minutes.  I've got to fix this so I don't get H&R's.

Link to comment
craigr Collaborator

craigr

Posted
Posted

I'm thinking this might be a PIA thing for the server I am using?  It's sporadic now all of my trackers shows all or most of the torrents I am seeding.  Or is this how it's supposed to work, assign and bind the port every ten minutes?

  

info] lu.privacy.network
[info] za.privacy.network
[info] aus-melbourne.privacy.network
[info] ae.privacy.network
[info] morocco.privacy.network

2024-07-23 20:16:15,234 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 20:16:55,860 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 23881 and VPN incoming port 25033 different, marking for reconfigure

2024-07-23 20:16:57,479 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: '10.28.112.194'
Configuration value successfully updated.

2024-07-23 20:16:57,479 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14f952eeaab0 current result: None>

2024-07-23 20:16:58,991 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2024-07-23 20:16:58,991 DEBG 'watchdog-script' stderr output:
<Deferred at 0x150e7d8ca300 current result: None>

2024-07-23 20:17:00,527 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (25033, 25033)
Configuration value successfully updated.

2024-07-23 20:17:00,527 DEBG 'watchdog-script' stderr output:
<Deferred at 0x1516ec3923c0 current result: None>

2024-07-23 20:17:02,929 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14693646ae40 current result: None>

2024-07-23 20:17:02,973 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2024-07-23 20:26:15,399 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 20:36:15,626 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 20:46:15,819 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 20:56:15,992 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 21:06:16,401 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 21:16:16,555 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 21:26:16,706 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 21:36:16,857 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 21:46:17,008 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 21:56:17,196 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 22:06:17,394 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

2024-07-23 22:16:17,549 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25033'

 

Link to comment
craigr Collaborator

craigr

Posted
Posted

So, looking back at old logs this has happened in the past from time to time.  What causes it?

  

2023-09-26 07:02:23,818 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 07:17:23,967 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 07:32:24,107 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 07:47:24,238 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 08:02:24,379 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 08:17:24,541 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 08:32:24,704 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

2023-09-26 08:47:24,883 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '32615'

 

Link to comment
binhex Mentor

binhex

Posted
  • Author
Posted
17 hours ago, craigr said:

Spoke too soon.  This is with zero changes:

  

2024-07-23 10:37:24,532 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2024-07-23 10:46:59,289 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23881'

2024-07-23 10:56:59,444 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '23881'

 

Every ten minutes.  I've got to fix this so I don't get H&R's.

That's totally expected, we need to poll the port at least every 15 minutes to keep it open, so to ensure we are within the 15 minutes period we poll every 10 minutes:- https://github.com/binhex/arch-int-vpn/blob/1c9a9a33d8bd53526766b128e8cd110507a945ca/run/local/tools.sh#L872-L875

 

EDIT - if it bothers you then i can set this to only be visible when DEBUG is set to true but it does no harm and shows you what your currently assigned  incoming port is.

 

  • Thanks 1
Link to comment
craigr Collaborator

craigr

Posted
Posted
4 hours ago, binhex said:

That's totally expected, we need to poll the port at least every 15 minutes to keep it open, so to ensure we are within the 15 minutes period we poll every 10 minutes:- https://github.com/binhex/arch-int-vpn/blob/1c9a9a33d8bd53526766b128e8cd110507a945ca/run/local/tools.sh#L872-L875

 

EDIT - if it bothers you then i can set this to only be visible when DEBUG is set to true but it does no harm and shows you what your currently assigned  incoming port is.

 

Thank you binhex.  I don't know why it never bothered me to the point of noticing before.  It's fine there.

 

If you have time to answer, has every version you have released done this?  It seems to not always occur looking back through a couple years of logs.

Link to comment
craigr Collaborator

craigr

Posted
Posted

Also binhex, I have been meaning to ask, is your Q&A number 21 and 22 up to date?  I can't get rid of the cypher error for example.

  

2024-07-23 23:49:40,899 DEBG 'start-script' stdout output:
2024-07-23 23:49:40 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 
2024-07-23 23:49:40 WARNING: file 'credentials.conf' is group or others accessible

 

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.

×
Go to topic listing
×
×
  • Create New...