34 minutes ago, binhex said:

Why not add airvpn dns to the list of 'NAME_SERVERS'?.

The container does not boot up properly if I configure the Airvpn server as DNS server. Worked just fine with Mullvad, does not work for Airvpn.

 

With Wireguard instead of OpenVPN it does work but the deluge web ui cannot be reached anymore.

Edited July 19, 20232 yr by Evidenz

14 minutes ago, Evidenz said:

The container does not boot up properly if I configure the Airvpn server as DNS server. Worked just fine with Mullvad, does not work for Airvpn.

i can only assume then that airvpn does not permit public access to their name servers, your only option is to use public name servers, keep in mind unless you are browsing and running other services over the vpn (using privoxy for instance) that may leak personal information then it really doesnt matter what name server you use, so what if google knows your vpn ip address is looking up the ip address for a index site, its of no consequence.

4 hours ago, Evidenz said:

For whatever reason my AirVPN config does not provide a dedicated DNS server? If I connect with the standard ovpn config provided by AirVPN DNS always defaults to the name servers stated in the docker config. Am I missing something?

I use airvpn with openvpn and have no issues. I always get the dedicated dns servers when I check https://ipleak.net/

Edit: But I don't have the name server variable in my template. Never needed it.

Edited July 19, 20232 yr by strike

Mullvad killed port forwarding this month. Didn't know about it until today when things didn't seem to be working right. 
Privoxy stopped functioning, for some reason, when port forwarding was removed? They said they were removing it July 1 but things didn't break until today. 

 

I redownloaded the wireguard config and everything seems to be running again. 

How bad is not having port forwarding going to screw me? Is it mostly torrent speeds?
 

11 minutes ago, sol said:

How bad is not having port forwarding going to screw me? Is it mostly torrent speeds?

Yeah, the speed is going to be affected and you probably won't be able to seed. 

Does anyone run multiple instances of delugevpn?? I have 2 running and downloading to seperate folders. One is for transcoding and viewing, the other is for longterm seeding. 

 

My problem is that I can't have both clients open in the same browser at the same time. I can only use incognito mode or another browser/device. Is this normal or is there some workaround for this?

I am a Nord user and have not been able to use this app since the last update. I receive a Auth Failed error in the log file. I have changed my password for nord down to the most basic of passwords 0 special characters letters and numbers only, Ive also checked to make sure the settings and the credentials.conf file are correct and matching... there is zero white space infront, behind, left, right, up, down, in the middle of the username and password. 

 

How do i downgrade back to the previous versions?

17 minutes ago, thesr5 said:

I am a Nord user and have not been able to use this app since the last update. I receive a Auth Failed error in the log file. I have changed my password for nord down to the most basic of passwords 0 special characters letters and numbers only, Ive also checked to make sure the settings and the credentials.conf file are correct and matching... there is zero white space infront, behind, left, right, up, down, in the middle of the username and password. 

 

How do i downgrade back to the previous versions?

Have nothing to do with the delugevpn version. https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=1277577

 

On 7/25/2023 at 10:52 AM, strike said:

Have nothing to do with the delugevpn version. https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=1277577

 

 

Oh, yup well there it is.. Thank you.

 

Edit: so yes this allowed the connection now and the WebUI is started but now when something starts to download it makes connection... starts to download and tapers off to 0 in about 10-15 seconds and never connects to any peers... what am i doing wrong now?

Edited July 27, 20232 yr by thesr5

2 hours ago, thesr5 said:

. starts to download and tapers off to 0 in about 10-15 seconds and never connects to any peers... what am i doing wrong now?

What location are you downloading to inside deluge, and where is that location mapped on the server?

 

Post the docker run and a screenshot of the deluge path settings if you are unclear.

I hope someone can provide some guidance on this issue which came up recently since upgrading to 6.12.2 my deluge client has just stopped loading for some reason.

The docker loads up and shows everything as all good but unable to load the web UI at all,

 

What info can I supply or any suggestions on how to fix? 

I can ping,

VPN connects and has IP

 

I have re-downloaded and removed the old appdata folder but but same results, 

 

8 hours ago, brent3000 said:

I hope someone can provide some guidance on this issue which came up recently since upgrading to 6.12.2 my deluge client has just stopped loading for some reason.

The docker loads up and shows everything as all good but unable to load the web UI at all,

 

What info can I supply or any suggestions on how to fix? 

I can ping,

VPN connects and has IP

 

I have re-downloaded and removed the old appdata folder but but same results, 

 

Do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

 

Also what network type do you use? And are you using VLAN?

Anyone using PIA? No longer able to download anything. I think I might need to change my OVPN file but looking for advise on which to use. I know they don't allow torrents on some servers, just can't find which are blocked.

I can't get the container to run, the container closes after 1 second, when i look at the logs it tells me:

 

"iptables v1.8.9 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)"

"Perhaps iptables or your kernel needs to be upgraded."

"2023-07-28 10:22:14.139993 [crit] iptables default policies not available, exiting script..."

 

I'm a complete noob at this, does anyone know how i can fix this?

23 hours ago, Kuwabara89 said:

Anyone using PIA? No longer able to download anything. I think I might need to change my OVPN file but looking for advise on which to use. I know they don't allow torrents on some servers, just can't find which are blocked.

Been using this container for quite some time now, and it works fine at my end.

Haven't changed the OVPN file since original install using DK and SE servers.

 

Is it all torrents that fails? 

Edited July 28, 20232 yr by CODEG33K

On 7/17/2023 at 2:42 AM, jherrinjr said:

Are you using privatevpn with wireguard also?

I managed to resolve my issue by competely deting the docker and config and recreating it

Sorry for adding another "cant get to the web ui" post but after a lot of digging I cant find an answer. 

 

Im running Unraid 6.12.3

Im using Windscribe VPN (ive use this with DelugeVPN in the past for years without issue)

I haven't used DelugeVPN for quite a while. Ive been using rTorrentVPN but it stopped working and I recently learned that is no more.

 

What I've tried: 

Updating my ovpn file... and tried lots of different places

Reinstalling the container and setting it back up.

Setting VPN_ENABLED to "no"

Drinking...

 

here is my log:

2023-08-06 17:46:19,423 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 Note: Treating option '--ncp-ciphers' as  '--data-ciphers' (renamed in OpenVPN 2.5).

2023-08-06 17:46:19,425 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 WARNING: file 'credentials.conf' is group or others accessible

2023-08-06 17:46:19,426 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 OpenVPN 2.6.5 [git:makepkg/cbc9e0ce412e7b42+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 13 2023
2023-08-06 17:46:19 library versions: OpenSSL 3.1.1 30 May 2023, LZO 2.10
2023-08-06 17:46:19 DCO version: N/A

2023-08-06 17:46:19,426 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-08-06 17:46:19,427 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 TCP/UDP: Preserving recently used remote address: [AF_INET]37.120.213.163:443

2023-08-06 17:46:19,428 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 Attempting to establish TCP connection with [AF_INET]37.120.213.163:443

2023-08-06 17:46:19,594 DEBG 'start-script' stdout output:
2023-08-06 17:46:19 TCP connection established with [AF_INET]37.120.213.163:443
2023-08-06 17:46:19 TCPv4_CLIENT link local: (not bound)
2023-08-06 17:46:19 TCPv4_CLIENT link remote: [AF_INET]37.120.213.163:443

2023-08-06 17:46:20,125 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 VERIFY OK: depth=2, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=Windscribe Node CA X1

2023-08-06 17:46:20,125 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 VERIFY OK: depth=1, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=Windscribe Node CA X2

2023-08-06 17:46:20,126 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 VERIFY KU OK
2023-08-06 17:46:20 Validating certificate extended key usage
2023-08-06 17:46:20 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-08-06 17:46:20 VERIFY EKU OK
2023-08-06 17:46:20 VERIFY X509NAME OK: C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=zrh-112.windscribe.com
2023-08-06 17:46:20 VERIFY OK: depth=0, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Systems, CN=zrh-112.windscribe.com

2023-08-06 17:46:20,631 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA256
2023-08-06 17:46:20 [zrh-112.windscribe.com] Peer Connection Initiated with [AF_INET]37.120.213.163:443

2023-08-06 17:46:20,971 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 TUN/TAP device tun0 opened
2023-08-06 17:46:20 net_iface_mtu_set: mtu 1500 for tun0

2023-08-06 17:46:20,971 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 net_iface_up: set tun0 up
2023-08-06 17:46:20 net_addr_v4_add: 10.121.60.40/23 dev tun0
2023-08-06 17:46:20 /root/openvpnup.sh tun0 1500 0 10.121.60.40 255.255.254.0 init

2023-08-06 17:46:20,976 DEBG 'start-script' stdout output:
2023-08-06 17:46:20 Initialization Sequence Completed
2023-08-06 17:46:20 Data Channel: cipher 'AES-256-GCM', peer-id: 0
2023-08-06 17:46:20 Timers: ping 5, ping-restart 60

2023-08-06 17:46:20,977 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN gateway IP addresses from tunnel...

2023-08-06 17:46:20,978 DEBG 'start-script' stdout output:
[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2023-08-06 17:46:22,005 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.121.60.40'

2023-08-06 17:46:22,006 DEBG 'start-script' stdout output:
[debug] Valid gateway IP address from tunnel acquired ''

2023-08-06 17:46:22,006 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-08-06 17:46:22,098 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-08-06 17:46:37,209 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.203.100'

2023-08-06 17:46:37,210 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-08-06 17:46:37,384 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.203.100'

2023-08-06 17:46:38,526 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 37.120.213.169

2023-08-06 17:46:38,528 DEBG 'start-script' stdout output:
[info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment

2023-08-06 17:46:38,599 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-08-06 17:46:38,608 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-08-06 17:46:38,609 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.121.60.40 different, marking for reconfigure

2023-08-06 17:46:38,613 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-08-06 17:46:38,618 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2023-08-06 17:46:38,622 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2023-08-06 17:46:38,622 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-08-06 17:46:38,871 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.111.128.41'
[info] Deluge key 'listen_interface' will have a new value '10.121.60.40'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-08-06 17:46:39,067 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'...

2023-08-06 17:46:39,260 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '92a4905269544d599638ddef384308dd'
[info] Deluge key 'default_daemon' will have a new value '92a4905269544d599638ddef384308dd'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-08-06 17:46:39,509 DEBG 'watchdog-script' stdout output:
[info] Deluge process started

2023-08-06 17:46:39,509 DEBG 'watchdog-script' stdout output:
[info] Waiting for Deluge process to start listening on port 58846...

 

If I open my log fast enough I also get this "insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory" further up in them.

 

 

I really hope this isn't a softball answer but Im at a loss. 

 

Thanks!

Edited August 7, 20232 yr by twistedlabel

7 hours ago, twistedlabel said:

If I open my log fast enough I also get this "insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory" further up in them.

i need the full log to really help you out, can you please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Hi, anyone here can help me? I got delugevpn installed and --net=container in qbittorrent. All is well but i cant access Qbittorrent webgui.

I am having an issue with Deluge. Upon a fresh reboot or array restart Deluge pings one core above 80% utilization, it jumps between core 0 and 12 but one of them will always be above 80%. If I stop the docker and restart it after, it corrects the issue. The first two pictures show the utilization prior to the docker being restarted, the third picture is after the docker restarts. Restarting the docker also brings down the CPU temps. 

 

Is there a way to correct this issue so i do not have to manually reboot the docker at every restart?

 

Rig details 

 

Intel Core i7-12700K | ASUS ROG Strix Z690-G Gaming WiFi | CORSAIR Vengeance 64GB (2 x 32GB) RAM DDR5 5200 | 5 - Seagate IronWolf Pro 12TB | SAMSUNG 980 PRO M.2 2TB (cache drive) | SAMSUNG 970 EVO PLUS m.2 250GB (VM drive) | MSI 2070 super (VM GPU) | WD Purple Pro 14 TB (VM Passthrough) | Sandisk Ultra Dual -64 GB (boot device)

6 hours ago, akhisyahmi said:

All is well but i cant access Qbittorrent webgui.

Read Q24 for full instruction:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

11 hours ago, binhex said:

Read Q24 for full instruction:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Hi, Thank you for your respond and I fix it already. Sorry for might asking a dumb question but I honestly new to this stuff. Thanks

21 hours ago, T_Matz said:

I am having an issue with Deluge. Upon a fresh reboot or array restart Deluge pings one core above 80% utilization, it jumps between core 0 and 12 but one of them will always be above 80%. If I stop the docker and restart it after, it corrects the issue. The first two pictures show the utilization prior to the docker being restarted, the third picture is after the docker restarts. Restarting the docker also brings down the CPU temps. 

 

Is there a way to correct this issue so i do not have to manually reboot the docker at every restart?

 

Rig details 

 

Intel Core i7-12700K | ASUS ROG Strix Z690-G Gaming WiFi | CORSAIR Vengeance 64GB (2 x 32GB) RAM DDR5 5200 | 5 - Seagate IronWolf Pro 12TB | SAMSUNG 980 PRO M.2 2TB (cache drive) | SAMSUNG 970 EVO PLUS m.2 250GB (VM drive) | MSI 2070 super (VM GPU) | WD Purple Pro 14 TB (VM Passthrough) | Sandisk Ultra Dual -64 GB (boot device)

I'm having the same issue, except restarting the container doesn't fix it, it eventually comes back chewing up core8 at 100%   
To add a bit more info i ran HTOP and it says its there are two processes, one sleeping, one running, both are  /user/bin python /user/bin/deluged -c /config -L info -l /config/deluged.log
I'm on a 13700k so i have plenty of other cores but still wondering what its doing.  I'm still running 6.11.5

6 hours ago, PassTheSalt said:

I'm having the same issue, except restarting the container doesn't fix it, it eventually comes back chewing up core8 at 100%   
To add a bit more info i ran HTOP and it says its there are two processes, one sleeping, one running, both are  /user/bin python /user/bin/deluged -c /config -L info -l /config/deluged.log
I'm on a 13700k so i have plenty of other cores but still wondering what its doing.  I'm still running 6.11.5

I've tested this a few times for me, upon reboot or restarting the array I will have a single core almost maxed, but after stopping deluge and restarting all cores will have normal utilization

Using ProtonVPN and occasionally natpmpc will fail, has anyone else encountered this? Not sure if this is a ProtonVPN issue or a Deluge issue.

This can go on for some time with Deluge unable to do any downloading/uploading meanwhile.

The only "fix" I've found seems to be to switch to another server but even then it can arise again until I happen to find one where it doesn't... until it happens again later on.

 

2023-08-10 18:56:03,452 DEBG 'start-script' stderr output:
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
  errno=11 'Resource temporarily unavailable'

2023-08-10 18:56:03,452 DEBG 'start-script' stdout output:
[warn] Unable to assign an incoming port for protocol UDP, returning 1 from function...
[warn] Unable to assign incoming port

2023-08-10 18:56:03,453 DEBG 'start-script' stdout output:
[info] 11 retries left
[info] Retrying in 10 secs...

 

2023-08-11 15:38:33,354 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 7 retries left

2023-08-11 15:38:35,706 DEBG 'start-script' stderr output:
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
  errno=11 'Resource temporarily unavailable'

2023-08-11 15:38:35,706 DEBG 'start-script' stdout output:
initnatpmp() returned 0 (SUCCESS)
using gateway : ***.***.***.***
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -7 (FAILED)

 

Edited August 11, 20232 yr by binguser