[Support] binhex - DelugeVPN


Recommended Posts

Posted (edited)
On 5/5/2022 at 8:56 PM, CBPXXIV said:

puzzled, been trucking along for a good while with delugevpn with zero issues.  Notice some stuff failed to download the other day so started poking around.  it seems that for some reason it's restarting like every 3-4 minutes.  I hadn't changed any settings, just started going wonky on me.  This is what I see in the logs, any thoughts?

 

2022-05-05 20:36:15,644 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-05-05 20:36:15,640 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-05-05 20:36:15,644 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-05-05 20:39:18,305 DEBG 'watchdog-script' stderr output:
malloc(): invalid next size (unsorted)

2022-05-05 20:39:46,523 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-05-05 20:39:46,529 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-05-05 20:39:46,642 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.3.112.248'
[info] Deluge key 'listen_interface' will have a new value '10.3.112.248'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-05 20:39:46,765 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'...

 

 

Best Regards,

-Knoxxiv

 

It appears I'm having this exact same issue.  Hangs at the same point and the WebUI doesn't load.

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 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'...


Sometimes, after leaving it for a few hours, it seems to move to the next step:

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 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-05-07 14:06:11,257 DEBG 'watchdog-script' stdout output:
[warn] Deluge config file /config/web.conf does not contain valid data, exiting Python script config_deluge.py...

2022-05-07 14:06:11,592 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-05-07 14:06:11,802 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started


However, the WebUI is not responsive and won't load.

I've made no changes to my configuration and it was working for many months before yesterday when this issue popped up.

 

Edit:  I was planning to follow the steps listed here today, but it seems to have started on it's own over night and is running fine now.  I'll update if that changes.

Edited by Earendur
Link to comment

I'm playing around with the console trying to set up some execute scripts and in trying out a couple of commands i keep getting the same error.

 

trying to resume a torrent that is currently paused i'm sending in the console

deluge console resume oertbgoyertboy792345796yg

and

deluge-console resume oertbgoyertboy792345796yg

gibberish being the hash or $torrentid in the execute script

 

both giving me the error message

Could not connect to daemon: 127.0.0.1:58846
   Password does not match

 

am i using the correct commands here or am i missing something?

Link to comment
Posted (edited)
On 5/7/2022 at 7:09 PM, Earendur said:

 

It appears I'm having this exact same issue.  Hangs at the same point and the WebUI doesn't load.

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 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'...


Sometimes, after leaving it for a few hours, it seems to move to the next step:

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 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-05-07 14:06:11,257 DEBG 'watchdog-script' stdout output:
[warn] Deluge config file /config/web.conf does not contain valid data, exiting Python script config_deluge.py...

2022-05-07 14:06:11,592 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-05-07 14:06:11,802 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started


However, the WebUI is not responsive and won't load.

I've made no changes to my configuration and it was working for many months before yesterday when this issue popped up.

 

Edit:  I was planning to follow the steps listed here today, but it seems to have started on it's own over night and is running fine now.  I'll update if that changes.

 

 

I've just seen exactly this behaviour (takes many minutes to progess from "[info] Writing changes to Deluge config file '/config/core.conf'...", WebUI nonresponsive, and deluge-web pinning one cpu core at 100%), and have found what was causing it for me.

 

'\appdata\binhex-delugevpn\web.conf' had grown to over 40MB causing both the config-parser script and deluge-web to choke trying to parse it. Looking at the file this was because there were thousands of 'session' entries; I'm guessing that it caches active sessions to the webui in the web.conf, but for some reason never clears them, causing the file to grow out of control.

 

Stopping the image, deleting all of these entries (bringing the file down to a much more reasonable 620bytes), and restarting the image made everything start up quickly with the webui working as normal.

 

Hopefully that's helpful to someone!

Edited by technoluddite
  • Like 1
Link to comment
8 hours ago, technoluddite said:

 

 

I've just seen exactly this behaviour (takes many minutes to progess from "[info] Writing changes to Deluge config file '/config/core.conf'...", WebUI nonresponsive, and deluge-web pinning one cpu core at 100%), and have found what was causing it for me.

 

'\appdata\binhex-delugevpn\web.conf' had grown to over 40MB causing both the config-parser script and deluge-web to choke trying to parse it. Looking at the file this was because there were thousands of 'session' entries; I'm guessing that it caches active sessions to the webui in the web.conf, but for some reason never clears them, causing the file to grow out of control.

 

Stopping the image, deleting all of these entries (bringing the file down to a much more reasonable 620bytes), and restarting the image made everything start up quickly with the webui working as normal.

 

Hopefully that's helpful to someone!

i don't have this issue but i was curious so i checked my web.conf as well.

i have 25,000 lines of session entries but the file is only 883kb. for your file to balloon past 40mb means you've got over 1,000,000 lines of session entries.

 

that definitely sounds to me like there's a different issue somewhere rather then it just being the active sessions never being cleared.

Link to comment
16 hours ago, technoluddite said:

Stopping the image, deleting all of these entries (bringing the file down to a much more reasonable 620bytes), and restarting the image made everything start up quickly with the webui working as normal.

so are you saying all sessions in that file can safely be deleted on startup? there are no cases where previous session info in the web.conf need to exist?, just asking as i dont actively use deluge any more so need somebody with first hand experience of this.

 

if this is the case then i can put in some code to clear session info down on startup.

Link to comment
57 minutes ago, binhex said:

so are you saying all sessions in that file can safely be deleted on startup? there are no cases where previous session info in the web.conf need to exist?, just asking as i dont actively use deluge any more so need somebody with first hand experience of this.

 

if this is the case then i can put in some code to clear session info down on startup.

I'm still on a crusty old release (2.0.4.dev38_g23a48dd01-3-01), but my web.conf only has 6 sessions and its the same install I've been using since 2017.

Link to comment
21 hours ago, technoluddite said:

 

 

I've just seen exactly this behaviour (takes many minutes to progess from "[info] Writing changes to Deluge config file '/config/core.conf'...", WebUI nonresponsive, and deluge-web pinning one cpu core at 100%), and have found what was causing it for me.

 

'\appdata\binhex-delugevpn\web.conf' had grown to over 40MB causing both the config-parser script and deluge-web to choke trying to parse it. Looking at the file this was because there were thousands of 'session' entries; I'm guessing that it caches active sessions to the webui in the web.conf, but for some reason never clears them, causing the file to grow out of control.

 

Stopping the image, deleting all of these entries (bringing the file down to a much more reasonable 620bytes), and restarting the image made everything start up quickly with the webui working as normal.

 

Hopefully that's helpful to someone!


Interesting.  Mine is 12 megabytes.

When you say you deleted the sessions, you went into the JSON and removed these records:

image.png.7dfc2b504b6b33069f8da65c5bf4940f.png

 

Of course, there are hundreds/thousands of these in the file.

I wonder if deleting the file itself would cause an issue, or if it would just recreate a new one?

I may leave them because the web ui is running, and watch it to see if they get cleaned up at all by the application.

Link to comment

Yeah, I removed the entire sessions key and its all sub-records. Not sure if the file would be recreated automatically correctly if you deleted it, I'd guess not as it contains the the password hash.

 

And yes the file was something like 1.2 millions lines, all but 23 of which were session records. Which now I think about it is far too many to just be orphaned sessions, even for an image that had been running (with irregular updates) since early 2019.

 

I suspect that any session records could be cleaned up safely on startup, worse case any active sessions would have to re-authenticate? I don't know for sure that there's nothing that depends on them though.

  • Upvote 1
Link to comment
On 5/10/2022 at 5:54 PM, technoluddite said:

Yeah, I removed the entire sessions key and its all sub-records. Not sure if the file would be recreated automatically correctly if you deleted it, I'd guess not as it contains the the password hash.

 

And yes the file was something like 1.2 millions lines, all but 23 of which were session records. Which now I think about it is far too many to just be orphaned sessions, even for an image that had been running (with irregular updates) since early 2019.

 

I suspect that any session records could be cleaned up safely on startup, worse case any active sessions would have to re-authenticate? I don't know for sure that there's nothing that depends on them though.


My file has now more than doubled.  It's 977,920 lines long, all but 25 or so lines are the sessions.  35 mbs in size.

Something is definitely not functioning correctly here.  These sessions shouldn't be accumulating like this and they should get cleaned up.

Link to comment

I've got an odd problem and wondering if anyone can help.

 

Yesterday my internet want really slow, it's usually about 70 down, 20 up, stored test was showing 6 down and 1 up instead!  I've discovered that the reason for this is that Deluge is constantly pulling 50-80mb/s. I have Google WiFi which is showing me device by device usage and the problem starts and ends when I turn the Docker container on and off.

 

When I open the console I can see it's really only downloading in the 5-10 mb/s range and there's nothing in the downloads folder that cous account for the 50Gb that I can see Deluge generated in a few hours yesterday.

 

I don't really know where to start with this, so hoping someone had some hints of advice?

 

Thanks.

Link to comment
Posted (edited)

I was able to get this container installed and running but the torrents start downloading at about 500kb/s and then just goes down until it just stops downloading. It doesn't even download 1%. I am running it on a Synology NAS and am using NordVPN. The log shows that it connects to the server but not sure why it won't download. Also the server I chose is a P2P server that I use on my laptop and phone with no issues.

 

I tried the instructions on this page but nothing has changed https://support.nordvpn.com/Connectivity/Proxy/1049258992/Proxy-setup-on-Deluge.htm

 

I was able to download the torrent files on my phone and laptop with no problem so I dont think the issue is with NordVPN, just not sure what I'm missing.
 

2022-05-15 18:21:22.514504 [info] System information Linux a5862a04f0d5 4.4.180+ #42218 SMP Mon Oct 18 19:17:56 CST 2021 x86_64 GNU/Linux,
2022-05-15 18:21:22.588216 [info] OS_ARCH defined as 'x86-64',
2022-05-15 18:21:22.666845 [info] PUID defined as '1026',
2022-05-15 18:21:22.752257 [info] PGID defined as '100',
2022-05-15 18:21:22.910946 [warn] UMASK not defined (via -e UMASK), defaulting to '000',
2022-05-15 18:21:22.993958 [info] Permissions already set for '/config',
2022-05-15 18:21:23.099544 [info] Deleting files in /tmp (non recursive)...,
2022-05-15 18:21:23.193740 [info] VPN_ENABLED defined as 'yes',
2022-05-15 18:21:23.292597 [info] VPN_CLIENT defined as 'openvpn',
2022-05-15 18:21:23.357587 [info] VPN_PROV defined as 'nordvpn',
2022-05-15 18:21:23.438826 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/us9310.nordvpn.com.udp.ovpn,
2022-05-15 18:21:23.583342 [info] VPN remote server(s) defined as '185.203.219.130,',
2022-05-15 18:21:23.644504 [info] VPN remote port(s) defined as '1194,',
2022-05-15 18:21:23.702126 [info] VPN remote protcol(s) defined as 'udp,',
2022-05-15 18:21:23.769724 [info] VPN_DEVICE_TYPE defined as 'tun0',
2022-05-15 18:21:23.838290 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS),
2022-05-15 18:21:23.918234 [info] LAN_NETWORK defined as '192.168.69.0/24',
2022-05-15 18:21:23.995429 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4',
2022-05-15 18:21:24.064957 [info] VPN_USER defined as 'MYUSER',
2022-05-15 18:21:24.130738 [info] VPN_PASS defined as 'MYPASS',
2022-05-15 18:21:24.204124 [info] ENABLE_PRIVOXY defined as 'yes',
2022-05-15 18:21:24.283409 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports,
2022-05-15 18:21:24.358764 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports,
2022-05-15 18:21:24.432818 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'debug',
2022-05-15 18:21:24.500678 [info] DELUGE_WEB_LOG_LEVEL defined as 'debug',
2022-05-15 18:21:24.579672 [info] Starting Supervisor...,
2022-05-15 18:21:26,384 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing,
2022-05-15 18:21:26,384 INFO Set uid to user 0 succeeded,
2022-05-15 18:21:26,396 INFO supervisord started with pid 9,
2022-05-15 18:21:27,400 INFO spawned: 'shutdown-script' with pid 177,
2022-05-15 18:21:27,403 INFO spawned: 'start-script' with pid 178,
2022-05-15 18:21:27,407 INFO spawned: 'watchdog-script' with pid 179,
2022-05-15 18:21:27,407 INFO reaped unknown pid 10 (exit status 0),
2022-05-15 18:21:27,420 DEBG 'shutdown-script' stdout output:,
[info] Signal not specified as parameter 2, assuming signal '15' (sigterm),
[info] Process owner not specified as parameter 3, assuming owner 'nobody',
,
2022-05-15 18:21:27,421 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs),
2022-05-15 18:21:27,422 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs),
2022-05-15 18:21:27,422 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs),
2022-05-15 18:21:27,449 DEBG 'watchdog-script' stdout output:,
[info] Deluge-web config file doesn't exist, copying default...,
,
2022-05-15 18:21:27,464 DEBG 'start-script' stdout output:,
[info] VPN is enabled, beginning configuration of VPN,
,
2022-05-15 18:21:27,472 DEBG 'watchdog-script' stdout output:,
[info] Deluge config file doesn't exist, copying default...,
,
2022-05-15 18:21:27,560 DEBG 'start-script' stdout output:,
[debug] Contents of ovpn file /config/openvpn/us9310.nordvpn.com.udp.ovpn as follows...,
,
2022-05-15 18:21:27,561 DEBG 'start-script' stdout output:,
client,
dev tun,

 

Edited by joelstitch
Link to comment
Posted (edited)

Just noticed that for the past 2 weeks or so, Sonarr and Radarr are no longer doing anything. I had errors connecting to deluge and jackett in both of them. Jackett seems to be on the way out so I switched to prowlarr. I am fairly sure that is set up correctly and I have it loaded in both Sonarr and Radarr. But nothing has changed with deluge. I can open the webui, but it will not connect to sonarr or radarr. Has something changed recently?

 

Update:

Actually, Deluge is messed up somehow. I can open the webui, but all the settings are blank and it keeps timing out. I can not add or edit anything.

 

Update 2:

Never mind. A server reset seems to have fixed it. 

Edited by jebusfreek666
updated info
Link to comment

OMG I can't win with this container. I was having the worst time trying to get it to work with NordVPN to the point that I went ahead and bought PIA. Followed the instructions for using DelugeVPN with PIA and I still can't get it to work. Other containers work fine except for this one. PLEASE SOMEONE HELP ME BEFORE I THROW MY LAPTOP OUT THE WINDOW!!!!!!

 

This are my logs:

 

2022-05-17 16:59:57,204 DEBG 'start-script' stdout output:,
2022-05-17 16:59:57 UDP link remote: [AF_INET]181.214.164.218:1198,
,
2022-05-17 16:59:57,299 DEBG 'start-script' stdout output:,
2022-05-17 16:59:57 [chicago415] Peer Connection Initiated with [AF_INET]181.214.164.218:1198,
,
2022-05-17 16:59:58,431 DEBG 'start-script' stdout output:,
2022-05-17 16:59:58 AUTH: Received control message: AUTH_FAILED,
2022-05-17 16:59:58 SIGTERM[soft,auth-failure] received, process exiting,
,
2022-05-17 16:59:58,434 DEBG 'start-script' stdout output:,
[info] Starting OpenVPN (non daemonised)...,
,
2022-05-17 16:59:58,447 DEBG 'start-script' stdout output:,
2022-05-17 16:59:58 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.,
,
2022-05-17 16:59:58,447 DEBG 'start-script' stdout output:,
2022-05-17 16:59:58 WARNING: file 'credentials.conf' is group or others accessible,
2022-05-17 16:59:58 OpenVPN 2.5.5 [git:makepkg/869f194c23ae93c4+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Dec 15 2021,
2022-05-17 16:59:58 library versions: OpenSSL 1.1.1m  14 Dec 2021, LZO 2.10,
,
2022-05-17 16:59:58,448 DEBG 'start-script' stdout output:,
2022-05-17 16:59:58 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts,
,
2022-05-17 16:59:58,450 DEBG 'start-script' stdout output:,
2022-05-17 16:59:58 TCP/UDP: Preserving recently used remote address: [AF_INET]181.214.164.218:1198,
2022-05-17 16:59:58 UDP link local: (not bound),
2022-05-17 16:59:58 UDP link remote: [AF_INET]181.214.164.218:1198,
,
2022-05-17 16:59:58,720 DEBG 'start-script' stdout output:,
2022-05-17 16:59:58 [chicago415] Peer Connection Initiated with [AF_INET]181.214.164.218:1198,
,
2022-05-17 16:59:59,762 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 AUTH: Received control message: AUTH_FAILED,
2022-05-17 16:59:59 SIGTERM[soft,auth-failure] received, process exiting,
,
2022-05-17 16:59:59,764 DEBG 'start-script' stdout output:,
[info] Starting OpenVPN (non daemonised)...,
,
2022-05-17 16:59:59,776 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.,
,
2022-05-17 16:59:59,776 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 WARNING: file 'credentials.conf' is group or others accessible,
,
2022-05-17 16:59:59,777 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 OpenVPN 2.5.5 [git:makepkg/869f194c23ae93c4+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Dec 15 2021,
,
2022-05-17 16:59:59,779 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 library versions: OpenSSL 1.1.1m  14 Dec 2021, LZO 2.10,
,
2022-05-17 16:59:59,781 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts,
,
,
,
2022-05-17 16:59:59,785 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 TCP/UDP: Preserving recently used remote address: [AF_INET]181.214.165.84:1198,
,
2022-05-17 16:59:59,785 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 UDP link local: (not bound),
,
2022-05-17 16:59:59,786 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 UDP link remote: [AF_INET]181.214.165.84:1198,
,
2022-05-17 16:59:59,975 DEBG 'start-script' stdout output:,
2022-05-17 16:59:59 [chicago407] Peer Connection Initiated with [AF_INET]181.214.165.84:1198,
,

 

Link to comment
1 hour ago, joelstitch said:

I still can't get it to work

 

1 hour ago, joelstitch said:
AUTH: Received control message: AUTH_FAILED,

PIA credentials aren't being accepted. I've always just used the same login and password that works on PIA's website, is that what you are using?

Link to comment
Posted (edited)
4 hours ago, JonathanM said:

 

PIA credentials aren't being accepted. I've always just used the same login and password that works on PIA's website, is that what you are using?

Yup. I tried the user and password they emailed me, no luck. Tried my email and password given, no luck. Tried username and new password, no luck. email and new password, no luck. No matter what I do I get the same error. I also tried different OVPN files that I downloaded from my user page in PIA website. Deleting the container, removing the folders, reinstalling with empty folders also did nothing.

 

Q16 on the FAQ didn't help. My username and password is right, the opvpn files I just downloaded straight from the website and the password doesnt have special characters or is too long.

Edited by joelstitch
Link to comment
38 minutes ago, joelstitch said:

I changed STRICT_PORT_FORWARD to no and now I am able to access Deluge and Download torrents. So far seems like is downloading well.

That sounds like you set your PIA endpoint to one that doesn't support port forwarding.

 

Port forwarding is important for seeding, without which will kill your download speed and overall standing on private trackers.

If you're only using public trackers, then I don't think it will impact much.

Link to comment
13 minutes ago, TranceGeniK said:

I think it has been changed automatically somehow

sorry to say, but there is no way this can happen, the container has no access to edit env vars defined on the host, this must be either CA plugin bug (unlikely) or PEBKAC

Link to comment
10 minutes ago, binhex said:

sorry to say, but there is no way this can happen, the container has no access to edit env vars defined on the host, this must be either CA plugin bug (unlikely) or PEBKAC

I'm still new to unraid and don't want to put the blame on anybody, just trying to help with how I managed to resolve the issue
I don't remember changing that env, so I assumed it was changed automatically, not sure how though...

Link to comment
11 minutes ago, TranceGeniK said:

I'm still new to unraid and don't want to put the blame on anybody, just trying to help with how I managed to resolve the issue

sure!, i appreciate the post, im just trying to be clear to anybody reading your post that the issue is not (and cannot be) the image 🙂

Link to comment

Currently using delugevpn and sabnzbdvpn running and both have mullvad vpn set up using wireguard. They both work great and i'm happy with it. I would like to route firefox, sonarr and radarr through delugevpn or sabnzbd using their privoxy but cant get it to work. Any tips please !

Link to comment
1 hour ago, Oggie said:

Currently using delugevpn and sabnzbdvpn running and both have mullvad vpn set up using wireguard. They both work great and i'm happy with it. I would like to route firefox, sonarr and radarr through delugevpn or sabnzbd using their privoxy but cant get it to work. Any tips please !

What are you using for the IP?

  • Thanks 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.