Hi All wonder if anyone can help with an issue i have encountered.

 

I have DelugeVPN setup and i have my SabNZBD going via this but im experiencing slow downloads when doing this if nothing is downloading via torrents SABNZBD runs at its normal speed but if Deluge is downloading the speed on SABNZDB drops from 13MB/s to 1MB/s meanwhile Deluge  is not getting above 400 KiB/s.

 

Does anyone know why this could be occuring

Hi there, I'm having an issue, my DelugeVPN Docker container stopped working!

 

 

2024-04-20 13:21:24,478 DEBG 'start-script' stdout output:
2024-04-20 13:21:24 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111)

2024-04-20 13:21:26,712 DEBG 'start-script' stdout output:
2024-04-20 13:21:26 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111)

2024-04-20 13:21:30,052 DEBG 'start-script' stdout output:
2024-04-20 13:21:30 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111)

2024-04-20 13:21:38,806 DEBG 'start-script' stdout output:
2024-04-20 13:21:38 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111)

 

Same message, but the number before DEBG changes each time.

 

Here it the error message I'm keep getting. Rebooting the server didn't solve the issue. I've looked online, and seen, that there was this issue a year ago, but there is no answer how to solve it...

 

I have completely reinstalled the docker container, but the issue persists.

 

Does anyone has an idea what to do?? I think it has something to do with read write permissions .. but I don't know what to change and how...

 

Edit: Don't know if important, but today I've restarted the server (adding more RAM). And additionally I've increased the docker virtual disk.

 

Edit2: Found a solution. In my case it seems that the VPN Provider Server, which was used for the past years, doesn't exist anymore. After reinstalling everything from scratch, I needed the new VPN Settings and found out, that my old server wasn't available anymore (couldn't find the .ovpn server file anymore).

 

Cheers!

Edited April 20, 20242 yr by Doublemyst
found solution

Hi!

I had this issue last year but fell sick so sadly had to drop troubleshooting. For that please forgive me. 

For some reason that I cannot fathom I'm unable to get Sonarr to route through Deluge VPN however, I've managed to get Radarr working through it fine. Below are steps that i've done. 

1. Gone to the Sonarr docker image, and under extra params added `--net=container:binhex-delugevpn`
2. Under the same Sonarr docker image, I've set the network type to `none`
3. Gone to the deluge vpn docker image, edited it and added port `8989` under `VPN_INPUT_PORTS` & `VPN_OUTPUT_PORTS`
4. Added another port for `TCP` under the same deluge vpn docker for port `8989`

When i visit the deluge vpn image ip address followed by `:8989`, it simply refuses to load. But when i do `:7878` (used by Radarr) for which i've followed the same process for as the above four steps it works. Its simply Sonarr that doesn't want to talk to the vpn image. FWIW I'm of-course using all binhex images for sonarr, radarr and deluge-vpn.

Any help would be appreciated. Thank you! 

Edited April 20, 20242 yr by Inch

18 minutes ago, Inch said:

Under the same Sonarr docker image, I've set the network type to `none`

If you set the network to bridge without changing anything else, does it work as expected, other than not running through the vpn?

2 minutes ago, JonathanM said:

If you set the network to bridge without changing anything else, does it work as expected, other than not running through the vpn?

Hi

Yes when i removed `--net=container:binhex-delugevpn`, and set the network to bridge, it works fine and goes through the first time setup. 

25 minutes ago, Inch said:

Added another port for `TCP` under the same deluge vpn docker for port `8989`

Show a screenshot of that in advanced view.

1 minute ago, JonathanM said:

Show a screenshot of that in advanced view.

Advanced view for the VPN image.

1 minute ago, Inch said:

Advanced view for the VPN image.

click edit on the 8989 entry and post just that part.

1 minute ago, JonathanM said:

click edit on the 8989 entry and post just that part.

2 minutes ago, Inch said:

Try deleting that and entering it again. It's missing the container port entry for some reason.

2 minutes ago, JonathanM said:

Try deleting that and entering it again. It's missing the container port entry for some reason.

Tried that, still doesn't show it. The same applies to the 7878 port that i added to the container for Radarr and thats working fine. It is showing container port under it though. 

2 minutes ago, Inch said:

Tried that, still doesn't show it.

Probably because you are using a custom network for delugevpn instead of the default bridge. Binhex doesn't support anything but plain bridge. Doesn't mean you can't make it work, but it can be challenging.

 

Maybe the radarr port was added while you were in plain bridge mode?

Just now, JonathanM said:

Probably because you are using a custom network for delugevpn instead of the default bridge. Binhex doesn't support anything but plain bridge. Doesn't mean you can't make it work, but it can be challenging.

 

Maybe the radarr port was added while you were in plain bridge mode?

I've tried plain bridge mode and custom network with the same results. I've just switched back to bridge, readded the sonarr port (specified 8989 in both) and it still doesn't work yet Radarr does still. 

1 minute ago, Inch said:

I've tried plain bridge mode and custom network with the same results. I've just switched back to bridge, readded the sonarr port (specified 8989 in both) and it still doesn't work yet Radarr does still. 

Strange. I'm out of things to try at this point. Maybe someone else will have some ideas.

4 minutes ago, JonathanM said:

Strange. I'm out of things to try at this point. Maybe someone else will have some ideas.

Np, thanks for trying! 

I forgot my web-gui password to binhex - DelugeVPN. I tried the following without success.

 

Quote

How can I reset forgotten password?

Stop the Web UI before modifying the web.conf file.

Edit web.conf in config and delete the entire pwd_sha1 line or use quick method via command-line e.g.:

sed -i.bak "/pwd_sha1/d" ~/.config/deluge/web.conf

Start the Web UI and the password will have been reset to default password deluge.

 

 I did not try the command-line since I don't know what I'm doing.

Any suggestion would be appreciated.

Hey y all !
So i am having this issue here :
First of all my deluge was not seeding, so i looked in the detail of the protonvpn and to add peertopeer i needed to add p2p to username, okay boom ! Done it works but now i have the following
When trying to add a torrent i got the not authorized error.
I do not know what do, did all updates, tried restarting all dockers. Still nothing thanks for the help !
 

 

2024-04-23 13:46:27,794 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2024-04-23 13:46:27,795 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2024-04-23 13:46:27,951 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.98.0.14'
[info] Deluge key 'listen_interface' will have a new value '10.98.0.14'
[info] Writing changes to Deluge config file '/config/core.conf'...

2024-04-23 13:46:28,125 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-04-23 13:46:28,305 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '14dceec26aea434e91fbe8879ac984c6'
[info] Deluge key 'default_daemon' will have a new value '14dceec26aea434e91fbe8879ac984c6'
[info] Writing changes to Deluge config file '/config/web.conf'...

2024-04-23 13:46:28,341 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2024-04-23 13:46:28,776 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2024-04-23 13:46:30,489 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14942c291f90 current result: None>

2024-04-23 13:46:30,558 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2024-04-23 13:46:30,559 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2024-04-23 13:46:30,559 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2024-04-23 13:46:30,560 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2024-04-23 13:46:31,567 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2024-04-23 13:46:31,575 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2024-04-23 13:47:24,407 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

2024-04-23 13:47:24,420 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/twisted/internet/defer.py", line 892, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3.11/site-packages/twisted/internet/defer.py", line 1371, in _cbDeferred
    self.callback(cast(_DeferredListResultListT, self.resultList))
  File "/usr/lib/python3.11/site-packages/twisted/internet/defer.py", line 696, in callback
    self._startRunCallbacks(result)
  File "/usr/lib/python3.11/site-packages/twisted/internet/defer.py", line 798, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/lib/python3.11/site-packages/twisted/internet/defer.py", line 892, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3.11/site-packages/deluge/ui/web/json_api.py", line 187, in _on_rpc_request_failed
    return self._send_response(request, response)
  File "/usr/lib/python3.11/site-packages/deluge/ui/web/json_api.py", line 229, in _send_response
    response = json.dumps(response)
  File "/usr/lib/python3.11/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python3.11/json/encoder.py", line 200, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.11/json/encoder.py", line 258, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.11/json/encoder.py", line 180, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
builtins.TypeError: Object of type Failure is not JSON serializable


2024-04-23 13:47:24,420 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:

Traceback (most recent call last):
Failure: deluge.error.NotAuthorizedError: Auth level too low: 0 < 5

 

The 2.1.1-5-01 update broke my YaRSS2 plugin.  I tried a few different versions of the egg and ways to name it, since it can be a bit fussy, but was unable to get it to enable.  Rolled back to 2.1.1-4-09 and it's working there.  

I run on UnRaid and have had zero problems for more than a year but after the most recent update of the container the client do not work as it should 😞

After seemingly succeeding to connect I see no list of torrents in progress and I cant add new torrents. I can however 

I see and even change the preferences.

 

In Deluged container log I see no errors but in the file config/deluged.log (that I can list when connecting to the container console) I find this:

 

Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.

 

Any tips?

 

Not sure if you are affeceted...
other people have reported issues with ssl / lets encrypt with vpn related dockers and changes. 

in essence, lets encrypt went regional for the ssl profile domain verification.

remake your ssl file and enable something, I think don't always use https?... as it more to do with how the tunnel first created.

https://forum.deluge-torrent.org/viewtopic.php?t=55467

 

 

Recently (probably since the last time I updated), I've noticed I can no longer add multiple torrent files at a time. If I select more than one torrent file, the final "add" button doesn't do anything. Anybody else noticing this?

Sadly im seeing this too since the last release, I've switched to using a monitored folder and have been adding the torrents there and they get picked up all at once. 

 

I didnt see anything in the logs but the browser console throws an error "TypeError: Cannot read properties of undefined (reading 'filename')"

Edited May 31, 20242 yr by Jasonwrigg

Hey everyone. Just updated to the new version of DelugeVPN and now I can't open the webGUI. I use PIA as my VPN client. I personally haven't changed any of the settings, just clicked "Update Container" or whatever through the Docker tab. Now when I click on webUI, I just get a "Connection Refused" error.

 

I opened the Docker logs and saw some SSL/TLS errors, but I'm not sure what they mean:

2024-06-05 09:19:37,831 DEBG 'start-script' stdout output:
2024-06-05 09:19:37 WARNING: file 'credentials.conf' is group or others accessible
2024-06-05 09:19:37 OpenVPN 2.6.10 [git:makepkg/ba0f62fb950c56a0+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Mar 20 2024
2024-06-05 09:19:37 library versions: OpenSSL 3.3.0 9 Apr 2024, LZO 2.10
2024-06-05 09:19:37 DCO version: N/A

2024-06-05 09:19:38,831 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-06-05 09:19:38,831 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 OpenSSL: error:068000E9:asn1 encoding routines::utctime is too short:
2024-06-05 09:19:38 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revocationDate, Type=X509_REVOKED
2024-06-05 09:19:38 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revoked, Type=X509_CRL_INFO
2024-06-05 09:19:38 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=crl, Type=X509_CRL

2024-06-05 09:19:38,832 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 OpenSSL: error:0488000D:PEM routines::ASN1 lib:
2024-06-05 09:19:38 CRL: cannot read CRL from file [[INLINE]]
2024-06-05 09:19:38 CRL: loaded 0 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----

2024-06-05 09:19:38 TCP/UDP: Preserving recently used remote address: [AF_INET]84.247.105.223:1198
2024-06-05 09:19:38 UDPv4 link local: (not bound)
2024-06-05 09:19:38 UDPv4 link remote: [AF_INET]84.247.105.223:1198

2024-06-05 09:19:38,923 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 VERIFY ERROR: CRL not loaded
2024-06-05 09:19:38 OpenSSL: error:0A000086:SSL routines::certificate verify failed:
2024-06-05 09:19:38 TLS_ERROR: BIO read tls_read_plaintext error
2024-06-05 09:19:38 TLS Error: TLS object -> incoming plaintext read error
2024-06-05 09:19:38 TLS Error: TLS handshake failed

2024-06-05 09:19:38,923 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 SIGHUP[soft,tls-error] received, process restarting

2024-06-05 09:19:38,923 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 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-06-05 09:19:38,923 DEBG 'start-script' stdout output:
2024-06-05 09:19:38 WARNING: file 'credentials.conf' is group or others accessible
2024-06-05 09:19:38 OpenVPN 2.6.10 [git:makepkg/ba0f62fb950c56a0+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Mar 20 2024
2024-06-05 09:19:38 library versions: OpenSSL 3.3.0 9 Apr 2024, LZO 2.10
2024-06-05 09:19:38 DCO version: N/A

2024-06-05 09:19:39,924 DEBG 'start-script' stdout output:
2024-06-05 09:19:39 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2024-06-05 09:19:39,924 DEBG 'start-script' stdout output:
2024-06-05 09:19:39 OpenSSL: error:068000E9:asn1 encoding routines::utctime is too short:
2024-06-05 09:19:39 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revocationDate, Type=X509_REVOKED
2024-06-05 09:19:39 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=revoked, Type=X509_CRL_INFO

2024-06-05 09:19:39,924 DEBG 'start-script' stdout output:
2024-06-05 09:19:39 OpenSSL: error:0688010A:asn1 encoding routines::nested asn1 error:Field=crl, Type=X509_CRL
2024-06-05 09:19:39 OpenSSL: error:0488000D:PEM routines::ASN1 lib:
2024-06-05 09:19:39 CRL: cannot read CRL from file [[INLINE]]
2024-06-05 09:19:39 CRL: loaded 0 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----

2024-06-05 09:19:39 TCP/UDP: Preserving recently used remote address: [AF_INET]172.64.151.73:1198
2024-06-05 09:19:39 UDPv4 link local: (not bound)
2024-06-05 09:19:39 UDPv4 link remote: [AF_INET]172.64.151.73:1198

 

The rest of my system is running fine, no issues with other containers. Diags posted in case they help.

mediavault-diagnostics-20240605-0920.zip

Edited June 5, 20242 yr by Arcaeus

11 minutes ago, Arcaeus said:

The rest of my system is running fine, no issues with other containers. Diags posted in case they help.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Hello,  Like Arcaeus, I'm unable to get into the deluge WebUI.  I get "This site can’t be reached" in chrome when trying to navigate to port 8112 on my hosts IP.  My difference from Arcaeus is that the install is completely new, so has never worked.   i use Proton as the VPN provider and the VPN, from what i can tell via command line, it working as expected.  I just can not access the WebUI for Deluge.

Command Execution.txt supervisord.log