Unraid: Access of the Webui only in bridge mode, not in custom br0

 

Hey there,

when I install delugevpn within Unraid (Docker) I can access the WebUi only when i use the bridge network mode, but then I cannot point Sonarr to delugevpn cause the connection is refused (says Sonarr).

When I use the custom br0 network mode (with 192.168.2.161), the WebUi is not accessible and Sonarr can't connect to delugevpn too.

I set the LAN_Network to the right internal network 192.168.2.0/24. No VPN is used to access the WebUI (FAQ Q25), privoxy is not used in the delugevpn-container (FAQ Q26).

My setup was working till I tested the Tailscale Plugin of Unraid, but i removed it in the meantime.

Maybe there are some leftovers?

Any hint is appreciated.

Mike

10 hours ago, DrGrimReaper said:

now i have everything being mounted in the container in /home for all my apps and i want to do it in this on as well and not in the /downloads 

you cannot bind mount /home in the container, that already exists and contains scripts required for the container to operate correctly, why are you bind mounting /home instead of using /downloads or /data to store incomplete and completed downloads?.

2 hours ago, mike175de said:

when I install delugevpn within Unraid (Docker) I can access the WebUi only when i use the bridge network mode, but then I cannot point Sonarr to delugevpn cause the connection is refused (says Sonarr).

you need to dig into this, this does work, but there any some tweaks you may need to make depending on how you have deluge configured.
 

2 hours ago, mike175de said:

My setup was working till I tested the Tailscale Plugin of Unraid, but i removed it in the meantime.

Maybe there are some leftovers?

I don't know too much about the tailscale integration that unraid does, and i have never used tailscale, having said that i have had some pointers from other people in this regards, Please see Q36 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[SOLVED] Unraid: Access of the Webui only in bridge mode, not in custom br0

 

For anybody running into the same issue:

 

Obviously the tailscale plugin did not delete all rules when uninstalling. The leftovers break the communication between containers running any kind of vpn, e.g. gluetun or delugevpn.

 

Solution:

1. Stop all containers and vms

2. Disable Docker and VMs function in settings

3. Flush the iptables (ip4 and ip6):

iptables --flush
iptables -t nat --flush
iptables -t mangle --flush
iptables -X
iptables -t nat -X
iptables -t mangle -X

ip6tables --flush
ip6tables -t nat --flush
ip6tables -t mangle --flush
ip6tables -X
ip6tables -t nat -X
ip6tables -t mangle -X

4. Reboot

5. Enable Docker and VMs function in setting

6. Normally all containers and vms will spin up, if not start them manually.

 

The missing iptables will be generated by Unraid itself and by Docker. All the access should be possible again.

Edited March 27, 20251 yr by mike175de
spelling

11 hours ago, binhex said:

you cannot bind mount /home in the container, that already exists and contains scripts required for the container to operate correctly, why are you bind mounting /home instead of using /downloads or /data to store incomplete and completed downloads?.

 

This is mostly due to the setup I configured a few years ago when I was using TrueNAS Scale. Since I do web design, scripting, and other tasks, I had everything set up and mounted in /home. A lot of my configurations and workflows are dependent on this directory, so I’d prefer not to change it. I also recently added a few remote paths in the *arr stack, and it seems to be working fine now with Deluge using /downloads

On 3/21/2025 at 11:18 PM, JonathanM said:

https://github.com/binhex/documentation/blob/master/docker/faq/help.md#gather-supervisor-log

Hi, thanks for the help.

Logs attached.

supervisord.log Edit.txt

Hi @binhex,

 

I have recently had my VPN go wibble; I was using an openvpn config file that worked fine for ages but just started getting errors about AES-256-CBC cipher. I've had this before and managed to fix it with a new config file, but thought it would be a good time to switch to Wireguard.

So I created the new wireguard config file, changed the config in unraid, uploaded my config file, and rebooted the Deluge docker follwinf the instructions at Q21 here. The logs see to show the wireguard connects fine and it loads the GUI according to the logs (attached below).

However, I can't access the GUI from my within my network - it just times out. I suspect I need to change a variable in the unraid docler config, but I'm not sure which. Screengrab of me setup attached too.

Any help much appreciated!

Unraid Binhex Deluge Load Log.txt

On 4/7/2025 at 10:28 PM, PitRejection2359 said:

Hi @binhex,

 

I have recently had my VPN go wibble; I was using an openvpn config file that worked fine for ages but just started getting errors about AES-256-CBC cipher. I've had this before and managed to fix it with a new config file, but thought it would be a good time to switch to Wireguard.

So I created the new wireguard config file, changed the config in unraid, uploaded my config file, and rebooted the Deluge docker follwinf the instructions at Q21 here. The logs see to show the wireguard connects fine and it loads the GUI according to the logs (attached below).

However, I can't access the GUI from my within my network - it just times out. I suspect I need to change a variable in the unraid docler config, but I'm not sure which. Screengrab of me setup attached too.

Any help much appreciated!

Unraid Binhex Deluge Load Log.txt 3.61 kB · 0 downloads

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

11 hours ago, binhex said:

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

192.168.0.3

11 hours ago, PitRejection2359 said:

192.168.0.3

Yep, that will be your problem then, from your screenshot:-



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

5 hours ago, binhex said:

Yep, that will be your problem then, from your screenshot:-



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

thank you so much - I've no idea how I managed to change that!

Is this docker PPA based?  One of my trackers has the following rules:

Deluge latest allowed recommended - version 1.3.1 through 2.1.x. Due to release stream issues, Versions 2.x Sourced from their PPA (or docker based on PPA) will not work here.

I can't connect to 90% of my indexers anymore on version 2.2.0-1-02. They all show either "Error: stream truncated" or they time out. Downloading Linux ISOs doesn't work either. Some public indexers and one private one still work though, weirdly. Reverting back to 2.1.1-8-03 fixes these issues for me. I get the same errors in binhex-qbittorrentvpn.

Did something change between these versions that could have caused this?

I just updated the docker and it is no longer working, it seems to freeze at the "NAME_SERVERS defined as" stage; it connects with my VPN and pulls IPs, but then nothing further. It sat for a couple hours after the update before I noticed it, so it's definitely not a "wait a little longer" issue. Restarted it and same deal...

On 5/1/2025 at 1:41 PM, TobiasGM said:

I can't connect to 90% of my indexers anymore on version 2.2.0-1-02. They all show either "Error: stream truncated" or they time out. Downloading Linux ISOs doesn't work either. Some public indexers and one private one still work though, weirdly. Reverting back to 2.1.1-8-03 fixes these issues for me. I get the same errors in binhex-qbittorrentvpn.

Did something change between these versions that could have caused this?

How did you revert back.  I know I have done it before but now I can't remember.

 

I cannot connect after the update.  Now I just orphaned my container and screwed the whole pooch.  My last backup is five days old and I had tons of custom paths in the container.  Crap!

 

I'm stuck here when it tries to load:

 

2025-05-02 23:58:55,919 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-toronto.privacy.network' is port forward enabled...

2025-05-02 23:59:11,110 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

 

9 hours ago, greyday said:

I just updated the docker and it is no longer working, it seems to freeze at the "NAME_SERVERS defined as" stage; it connects with my VPN and pulls IPs, but then nothing further. It sat for a couple hours after the update before I noticed it, so it's definitely not a "wait a little longer" issue. Restarted it and same deal...

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

7 hours ago, craigr said:

How did you revert back.  I know I have done it before but now I can't remember.

 

I cannot connect after the update.  Now I just orphaned my container and screwed the whole pooch.  My last backup is five days old and I had tons of custom paths in the container.  Crap!

 

I'm stuck here when it tries to load:

 

2025-05-02 23:58:55,919 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-toronto.privacy.network' is port forward enabled...

2025-05-02 23:59:11,110 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

 

You can revert back to a previous version by going to the docker tab, editing the deluge container and adding a tag after the repository name. Changing the repository from "binhex/arch-delugevpn" to "binhex/arch-delugevpn:2.1.1-8-03" reverts back to the version I mentioned. You can find a list of releases with their tags here: binhex/arch-delugevpn/releases

@craigr You can re-add orphaned containers by the way, without loosing your previous settings. You just need to click on "Add Container" at the bottom of the docker tab and choose the orphaned container/template from the list of templates.

2 hours ago, TobiasGM said:

You can revert back to a previous version by going to the docker tab, editing the deluge container and adding a tag after the repository name. Changing the repository from "binhex/arch-delugevpn" to "binhex/arch-delugevpn:2.1.1-8-03" reverts back to the version I mentioned. You can find a list of releases with their tags here: binhex/arch-delugevpn/releases

 

Thank you.  This is exactly what I did when my container got orphaned though.  I'll try again.

 

1 hour ago, TobiasGM said:

@craigr You can re-add orphaned containers by the way, without loosing your previous settings. You just need to click on "Add Container" at the bottom of the docker tab and choose the orphaned container/template from the list of templates.

 

I know but... I've been sick, and I was very tired... and I deleted the orphan 😭

 

Not a good night last night.  Thanks for your help.

I should have stopped at 11:30 when things weren't working and walked away.  I was so tired and felt like such garbage.  It's not my style to quit, but all I did was make a mess.

Well that was fun.  It looks like I have everything back up mostly.  I am getting this security error once deluge starts up that I don't recall seeing before.  How may I fix it?

 

2025-05-03 11:37:09,420 DEBG 'watchdog-script' stderr output:
/usr/lib/python3.13/site-packages/pkg_resources/__init__.py:1490: UserWarning: Extraction path is writable by group/others and vulnerable to attack when used with get_resource_filename (/config/python-eggs). Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
  warnings.warn(msg, UserWarning)

 

Thanks TobiasGM!

 

 

binhex, I'll try and get you a complete log after upgrading.  As I posted above, this is where it would freeze on your current version after I updated last night.  Version 2.1.1-8-03 is working fine here again now.  I did so much backing up and restoring that I may have overwritten or deleted the complete log in my tired attempt to get things fixed last night.

 

Quote

2025-05-02 23:58:55,919 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-toronto.privacy.network' is port forward enabled...

2025-05-02 23:59:11,110 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

 

 

Edited May 3, 20251 yr by craigr

8 hours ago, 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

I found a log for my issue.  Key time is 2025-05-02 23:59:11, that's where it stops.  The lines below are me stopping the container.

supervisord.log

48 minutes ago, craigr said:

I found a log for my issue.  Key time is 2025-05-02 23:59:11, that's where it stops.  The lines below are me stopping the container.

supervisord.log 11.63 kB · 2 downloads

ok for some reason the container seems unable to connect to PIA to get the list of port forward enabled endpoints and as you have STRICT_PORT_FORWARD set to 'yes' the script cannot continue.

from your log:-
2025-05-02 23:59:11,110 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

So try opening a web browser and see if you can get back a response from url https://serverlist.piaservers.net/vpninfo/servers/v4, it will be in json format, i just checked it and its live for me so if it doesn't return anything then something is blocking on your network.

If it does return then try restarting the container, you may of just attempted connection when the api was down.

2 hours ago, craigr said:

I know but... I've been sick, and I was very tired... and I deleted the orphan

BTW deleting the container, or the image or both should result in zero configuration and data loss, both are expendable items, clicking on 'add container' and then selecting your template from the 'user templates' section would get you back up and running within minutes (seconds if you dont delete the image).