Just looking over some of the recent posts, was there something major breaking in the latest release? suddenly all my indexers are all offline and I'm getting a bunch of errors now when I try and validate VPN using containers e.g.

"Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. The SSL connection could not be established, see inner exception"

This has taken off all my trackers :/

I also get this error when trying to validate with Flaresolverr

"Unable to connect to proxy: Connection refused (<ip of the VPN Container>:8191). Check the log surrounding this error for details"

But I can validate all of my other clients which are not sitting on the VPN container

Edited June 8, 20251 yr by brent3000
added more info

On 6/1/2025 at 9:11 AM, sabonim38 said:

After updating from unraid 7.1.0rc4 to 7.1.2, I'm not able to connect to my deluge webui anymore. Any one know what the problem could be?

If I roll back, I can access deluge webui again.

Same here. Been running great for years, then I update to a new OS version and can't access the WebUI.

Not sure where to go from here. Have you been able to figure this out?

Have you guys tried using the test version at all? Update the Docker Repository path to add ':test' to the end of it. I was having issues but this version has been working great for me so far.

2 hours ago, RainDess said:

Have you guys tried using the test version at all? Update the Docker Repository path to add ':test' to the end of it. I was having issues but this version has been working great for me so far.

Just pulled down that test version and same issue - WebUI cannot be reached.

13 hours ago, BBLV said:

Same here. Been running great for years, then I update to a new OS version and can't access the WebUI.

Not sure where to go from here. Have you been able to figure this out?

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,

having the same issue, fresh install after upgrading unraid to the newest version, logs make it seem like everything is fine but I can't connect to the webui.

Attaching my logs.supervisord.log

I would appreciate any and all help, thank you.

49 minutes ago, nana said:

Hello,

having the same issue, fresh install after upgrading unraid to the newest version, logs make it seem like everything is fine but I can't connect to the webui.

Attaching my logs.supervisord.log

I would appreciate any and all help, thank you.

what is the ip address of the machine running the web browser?

Edit- solved but posted anyhow.. in case someone else can benefit.. i updated to latest stable version of unraid 7.1.4 - i am not sure but pretty sure this is what broke my deluge-vpn. I can't roll back for a few days until parity check finishes. I can connect via web ui, but no longer through the deluge thin client. Also it has broken my privoxy which i use to connect to vpn on chrome using proxy by patterns. -FOUND SOLUTION.... disconnected tailscale on my windows 11 machine and it all works fine.. - so i will try and figure out to have tailscale and privoxy/deluge client work in harmony next.

On 6/28/2025 at 1:21 AM, binhex said:

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

Log attached.

supervisord.log

On 6/28/2025 at 10:16 PM, binhex said:

what is the ip address of the machine running the web browser?

192.168.0.204

2 hours ago, nana said:

192.168.0.204

then thats your issue, incorrect LAN_NETWORK, from your log:

2025-06-28 12:14:32.452942 [info] LAN_NETWORK defined as '192.168.1.0/24

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

On 6/30/2025 at 6:51 PM, BBLV said:

Log attached.

supervisord.log

looks like the remote endpoint you are trying to connect to is not in a good state, from your log:

2025-06-30 10:44:21,092 DEBG 'start-script' stdout output:

2025-06-30 10:44:21 UDPv4 link remote: [AF_INET]64.188.16.131:443

2025-06-30 10:44:21,103 DEBG 'start-script' stdout output:

2025-06-30 10:44:21 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111)

my advise is to download a new openvpn config file for another endpoint.

13 minutes ago, binhex said:

looks like the remote endpoint you are trying to connect to is not in a good state, from your log:

2025-06-30 10:44:21,092 DEBG 'start-script' stdout output:

2025-06-30 10:44:21 UDPv4 link remote: [AF_INET]64.188.16.131:443

2025-06-30 10:44:21,103 DEBG 'start-script' stdout output:

2025-06-30 10:44:21 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111)

my advise is to download a new openvpn config file for another endpoint.

I haven't changed anything except updating the OS, so it's odd that it would randomly have that issue. I haven't checked into Tailscale yet, but would you recommend moving to it from OpenVPN? It may fix my issue?

On 6/4/2025 at 10:21 PM, SliMat said:

So, none of them are called xxxxxxxxx.privacy.network - so from the list of endpoints which support port forwarding it lists - nl-netherlands-so.privacy.network

Thats because one is a listing of openvpn config files, and one is a listing of the actual remote endpoints you connect to.

11 hours ago, BBLV said:

I haven't changed anything except updating the OS, so it's odd that it would randomly have that issue.

That's because the change is not on your end, its with your VPN provider, they have modified/deleted/broken the endpoint you are connecting to, re-download the openvpn config file from your vpn provider.

8 hours ago, binhex said:

That's because the change is not on your end, its with your VPN provider, they have modified/deleted/broken the endpoint you are connecting to, re-download the openvpn config file from your vpn provider.

Redid the whole process with new VPN credentials and new OpenVPN config file and we're back up and running! Thanks for the help, yet again.

Just updated unraid from 7.0.1 to 7.1.4 and i started sometimes getting unraid syslog errors when a torrent changes download folder. deluge changes the torrent state to "error" and the "status" bar says "Error: Failed to move download folder: Numerical result out of range". this was also reported in 7.1.0 but for a different container so im unsure if its specifically a delugevpn issue or an unraid issue.

if you believe this is a delugevpn issue i can proceed with the logs etc.

1 hour ago, MammothJerk said:

Just updated unraid from 7.0.1 to 7.1.4 and i started sometimes getting unraid syslog errors when a torrent changes download folder. deluge changes the torrent state to "error" and the "status" bar says "Error: Failed to move download folder: Numerical result out of range". this was also reported in 7.1.0 but for a different container so im unsure if its specifically a delugevpn issue or an unraid issue.

if you believe this is a delugevpn issue i can proceed with the logs etc.

sounds like a unraid issue to me.

(I am here because I have a question regarding DelugeVPN, but unrelated to Unraid, hope this is still the right place)

I use DelugeVPN for years on a Debian server (so not Unraid). It works great.

I noticed that it uses quite a lot of CPU, nothing spectacular but still 3-5 times the usage of other containers.

This is not a problem but I am curious if this is expected. I can imagine that the CPU usage comes from the en/decryption of the traffic but I checked right now and it is south of 0.5 Mbps.

Again - everything works fine, it is more a curiosity from my side (and who knows, maybe something to tweak to bring the number down?)

Edited July 7, 2025Jul 7 by Wpq

On 7/7/2025 at 2:04 AM, MammothJerk said:

Just updated unraid from 7.0.1 to 7.1.4 and i started sometimes getting unraid syslog errors when a torrent changes download folder. deluge changes the torrent state to "error" and the "status" bar says "Error: Failed to move download folder: Numerical result out of range". this was also reported in 7.1.0 but for a different container so im unsure if its specifically a delugevpn issue or an unraid issue.

if you believe this is a delugevpn issue i can proceed with the logs etc.

I have the same issue after upgrading. I use binhex-qbittorrentvpn as well and that container is working fine.

Edited July 9, 2025Jul 9 by ElementBreaker

On 7/1/2025 at 10:53 PM, binhex said:

then thats your issue, incorrect LAN_NETWORK, from your log:

2025-06-28 12:14:32.452942 [info] LAN_NETWORK defined as '192.168.1.0/24

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

Thank you, this solved my issue!

Hello guys,

I have had Unraid version 6.8.0 hosted on Supermicro X9DR3-F Version 0123456789 running very stable without any issues since 2019.

Couple of days back, I've noticed I couldn't pull up binhex-delugevpn docker container in UI.

So, I thought of upgrading to latest stable version. So, as part of upgrade process, I've upgraded all the plugins and docker container whatever they could upgrade. Since not all of them were backwards compatible with 6.8.0 version.

The default version presented by Unraid to upgrade to was 7.0.1 -which I did.

I have searched few forums and decided to backup and reinstall the docker image and reinstall all the containers.

Looks like OpenVPN is deprecated and I have installed WireGuard-Docker in it's place.

I've re-installed deluge first and later sabnzbdvpn containers.,

After the upgrade, I've noticed the following issues:

1) binhex-delugevpn UI comes up, but its not downloading any torrents. For some torrents, the download speed is at 1kb/sec....but literally there is no progress.

I've tried reinstalling again with OpenVPN with copying latest credentials, but still it isn't downloading any torrents.

I suspect it might be incorrect configuration with ports or keys of wireguard vpn / Open vpn.

2) binhex-sabnzbdvpn is the only container that did not start. It's logs also doesn't show anything. Currently it's stopped.

sabnzbdvpn failed and the log states
"Bind for 0.0.0.0:9118 failed: port is already allocated."
When I checked deluge configuration, it's using this for microsocks.

Container Port: 9118
This is the port for microsocks application - Socks5 proxy server.

How do I resolve this conflict / sharing of 9118 port between deluge and sabnzbdvpn.
I've attached the log and the docker allocation of ports

deluge_log_071425.txt

Edited July 15, 2025Jul 15 by KevinImf

10 hours ago, KevinImf said:

sabnzbdvpn failed and the log states
"Bind for 0.0.0.0:9118 failed: port is already allocated."
When I checked deluge configuration, it's using this for microsocks.

Container Port: 9118
This is the port for microsocks application - Socks5 proxy server.

How do I resolve this conflict / sharing of 9118 port between deluge and sabnzbdvpn.

simple, you change the port on the host side to be a non conflicting port number, for example 9119 (assuming 9119 is not in use by another container).

10 hours ago, KevinImf said:

binhex-delugevpn UI comes up, but its not downloading any torrents. For some torrents, the download speed is at 1kb/sec....but literally there is no progress.

I've tried reinstalling again with OpenVPN with copying latest credentials, but still it isn't downloading any torrents.

i would suspect /mnt/disks/WDC... is not healthy or not mounted, check that you can write to it.

On 7/15/2025 at 9:50 AM, binhex said:

simple, you change the port on the host side to be a non conflicting port number, for example 9119 (assuming 9119 is not in use by another container).

i would suspect /mnt/disks/WDC... is not healthy or not mounted, check that you can write to it.

When I upgraded unraid, looks like the change the share/mount name of my Unassigned drives.
Reversering the mount /share name back to the previous one, fixed the deluge issue.
Also, assigned a different port to sabnbzd and it's also working fine now.

I really appreciate your suggestion. I would have never thought it would have been drive mounting issue. I was focused on ports and vpn configurations.

Thank you!!

On 6/8/2025 at 11:06 PM, brent3000 said:

Just looking over some of the recent posts, was there something major breaking in the latest release? suddenly all my indexers are all offline and I'm getting a bunch of errors now when I try and validate VPN using containers e.g.

"Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. The SSL connection could not be established, see inner exception"

This has taken off all my trackers :/

I also get this error when trying to validate with Flaresolverr

"Unable to connect to proxy: Connection refused (<ip of the VPN Container>:8191). Check the log surrounding this error for details"

But I can validate all of my other clients which are not sitting on the VPN container

Just hoping to re-tag this, still having very odd issues where my prowlarr and flaresolverr dont seem to be resolving via the VPN client