19 hours ago, strike said:

First, change your vpn password (and user if you can), as you forgot to redact them from the log. Second, set STRICT_PORT_FORWARD to no. And thrid, see Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thank you, ultimately what fixed it was replacing an outdated config file. I appreciate the help!

17 hours ago, strike said:

But why are you messing with input/output ports then? That should only be used if the containers are behind the delugevpn container.

Behind Deluge I have Prowlarr and Flaresolvarr which is also unable to connect (which is what the ports are used for) but also if the VPN is enabled would I not need to have the ports for input set for the external containers to access Deluge? or is Deluge not considered behind the VPN?

17 hours ago, strike said:

Have you enabled host access to custom networks in settings-Docker?

Yes this is enabled

17 hours ago, strike said:

Do you have proxy enabled in sonarr/radarr?

No I have not as I didnt know this was considered a proxy and didnt know the settings how to apply that as a proxy? I normally would think of something like nginx as a proxy but this I considered as just like I would connect to the WebUI using the IP it would be the same concept. Can you advise how the proxy settings should be setup when communicating with an app behind the VPN? I assumed if all the ports and containers were mapped they would flow the IP across (LIke when I access the WebUI for Prowlerr it works fine no issues, but asking to verify a site then fails.

5 hours ago, brent3000 said:

Behind Deluge I have Prowlarr and Flaresolvarr which is also unable to connect (which is what the ports are used for) but also if the VPN is enabled would I not need to have the ports for input set for the external containers to access Deluge? or is Deluge not considered behind the VPN?

Yes this is enabled

No I have not as I didnt know this was considered a proxy and didnt know the settings how to apply that as a proxy? I normally would think of something like nginx as a proxy but this I considered as just like I would connect to the WebUI using the IP it would be the same concept. Can you advise how the proxy settings should be setup when communicating with an app behind the VPN? I assumed if all the ports and containers were mapped they would flow the IP across (LIke when I access the WebUI for Prowlerr it works fine no issues, but asking to verify a site then fails.

You don't need to set up proxy, the reason I asked is because if enabled it can cause connection issues if not set properly.

Please post a new log, remember to redact user/pw

So this happened last night I got up this morning and nothing Deluge was not connected would not load the web ui, same for me I Variable: VPN_ENABLED: no and the web ui loads, set it to yes and I get an error message

2026-08-07 11:31:47 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

2026-08-07 11:31:47 TLS Error: TLS handshake failed.

This all started sometime last night after a system reboot.

8 minutes ago, Salty69 said:

So this happened last night I got up this morning and nothing Deluge was not connected would not load the web ui, same for me I Variable: VPN_ENABLED: no and the web ui loads, set it to yes and I get an error message

2026-08-07 11:31:47 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

2026-08-07 11:31:47 TLS Error: TLS handshake failed.

This all started sometime last night after a system reboot.

Need a full log, please do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Strike:

Here are the 2 logs you asked for.

docker run.txt supervisordlog.txt

17 minutes ago, Salty69 said:

Strike:

Here are the 2 logs you asked for.

I can't see any other errors in the log besides the TLS handshake error. This can usually be solved by downloading a new .ovpn file from your vpn provider. I tried to ping the most recent server you connected to in your log, and it confirmed it's down.

2 hours ago, strike said:

I can't see any other errors in the log besides the TLS handshake error. This can usually be solved by downloading a new .ovpn file from your vpn provider. I tried to ping the most recent server you connected to in your log, and it confirmed it's down.

2 hours ago, strike said:

I can't see any other errors in the log besides the TLS handshake error. This can usually be solved by downloading a new .ovpn file from your vpn provider. I tried to ping the most recent server you connected to in your log, and it confirmed it's down.

Thanks I'll give it a try, if I can remember how to do it.

18 hours ago, Salty69 said:

Thanks I'll give it a try, if I can remember how to do it.

18 hours ago, Salty69 said:

20 hours ago, strike said:

I can't see any other errors in the log besides the TLS handshake error. This can usually be solved by downloading a new .ovpn file from your vpn provider. I tried to ping the most recent server you connected to in your log, and it confirmed it's down

Strike, Just an update I downloaded the new link from my VPN and installed it and everything work as it should thanks for your help with this hopefully, I will remember how to fix it if or when it happens again.

thanks again

George

Hello! I was directed here by a kind soul on the Deluge forums who said I was more likely to find a fix here than there.

I'm running ZimaOS. I had followed a youtube video guide and ran into a handful of random problems, so I decided to just format and Start from Scratch with the binhex versions as directed by the Deluge forums.

I followed the binhex/arch-delugevpn instructions, setting the appropriate environmental variables. I have the paid tier of ProtonVPN. I generated the wireguard conf file from ProtonVPN with NAT-PMP on and VPN Accelerator on. I put the wg0 file into the wireguard folder generated when I installed Deluge. I restarted the whole system and tried to open Deluge.

EDIT: this problem self-resolved when I updated to ZimaOS 1.7.0. Now when I try to run DelugeVPN with VPN "on" I am unable to access the webUI from within my LAN. With VPN_ENABLED off, I can access the webUI. Please see more recent comment. Thank you!

Edited Saturday at 03:18 PM4 days by Johnfest
Problem resolved; new problem arose. See new comment.

On 8/13/2026 at 6:00 PM, Johnfest said:

The application is not running properly. We recommend checking:

All configuration items (e.g., port, path).
The access permissions of the storage directories.
The connection settings for dependent services like the database.

Please check the detailed startup logs in the "Configuration" menu to identify the specific issue.

This message is not coming from delugevpn I don't think. What are you using to manage your containers?

If you disable the vpn, can you get to the webui? What network type do you use and what is the IP of the computer you're trying to access deluge webui?

Edit: This here from your log is an issue tho, the vpn is not going to work correctly if iptables is not working.

Have you checked your permissions?

delugevpn | modprobe: FATAL: Module ip6_tables not found in directory /lib/modules/6.18.9 delugevpn | ip6tables v1.8.11 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?) delugevpn | Perhaps ip6tables or your kernel needs to be upgraded.

Edited Friday at 04:31 PM5 days by strike

1 hour ago, strike said:

This message is not coming from delugevpn I don't think. What are you using to manage your containers?

If you disable the vpn, can you get to the webui? What network type do you use and what is the IP of the computer you're trying to access deluge webui?

I'm using ZimaOS; its UI manages all of the containers.

Yes, if I change the environmental variable "ENABLE_VPN" to "no" I am able to get to the Deluge webui.

Forgive me if I don't understand exactly what you're asking when you say "what network type do you use?"

I have a modem from my ISP connected to a Netgear router with a satellite. My Zima machine is 192.168.1.24 on my LAN. Does that answer the question?

Thanks for your help!

EDIT:

I turned on my machine to day and was prompted to update ZimaOS to 1.7.0, so I did.

Now when I try to start Deluge, I get "Unable to connect" from my browser (tried multiple browsers and multiple devices to access it). When I look at the log, the FATAL error from before is gone; it looks like Deluge is starting but that I can't open the webUI when it does. I assume this has to do with the VPN and my network/port/firewall settings but I don't know where to start to fix it.

If I set "VPN_ENABLED" to "no" I am able to start Deluge and access the webUI no problem.

https://www.logpasta.com/paste/1d7f80b8-c6bf-40c2-9b45-8126befe7d55

Edited Friday at 08:01 PM5 days by Johnfest

21 hours ago, Johnfest said:

I'm using ZimaOS; its UI manages all of the containers.

Yes, if I change the environmental variable "ENABLE_VPN" to "no" I am able to get to the Deluge webui.

Forgive me if I don't understand exactly what you're asking when you say "what network type do you use?"

I have a modem from my ISP connected to a Netgear router with a satellite. My Zima machine is 192.168.1.24 on my LAN. Does that answer the question?

Thanks for your help!

EDIT:

I turned on my machine to day and was prompted to update ZimaOS to 1.7.0, so I did.

Now when I try to start Deluge, I get "Unable to connect" from my browser (tried multiple browsers and multiple devices to access it). When I look at the log, the FATAL error from before is gone; it looks like Deluge is starting but that I can't open the webUI when it does. I assume this has to do with the VPN and my network/port/firewall settings but I don't know where to start to fix it.

If I set "VPN_ENABLED" to "no" I am able to start Deluge and access the webUI no problem.

https://www.logpasta.com/paste/1d7f80b8-c6bf-40c2-9b45-8126befe7d55

The log looks better now. And by what network type you use, I meant what docker network type are you using? Host/bridge or custom network. You should be using bridge.

Have you done this part?

If you wish to use WireGuard (defined via 'VPN_CLIENT' env var value ) then due to the enhanced security and kernel integration WireGuard will require the container to be defined with privileged permissions and sysctl support, so please ensure you change the following docker options:-

from

    --cap-add=NET_ADMIN \

to

    --sysctl="net.ipv4.conf.all.src_valid_mark=1" \
    --privileged=true \

1 hour ago, strike said:

The log looks better now. And by what network type you use, I meant what docker network type are you using? Host/bridge or custom network. You should be using bridge.

Have you done this part?

Yes I'm using Bridge.

Yes I did that part.

I also went through the entire FAQ here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

In the interest of making sure I didn't miss anything, here's my take on every question there. I italicized the two that I think could be relevant but which I already checked; and I bolded the one that stood out but I'm not sure whether it applies:
Q1 is about Kill Switches and doesn't apply

Q2 is about accessing from OUTSIDE the LAN; but I'm inside

Q3 is about Privoxy which I have turned "off" and I don't think is relevant

[i]Q4 is about the LAN_NETWORK environmental variable and just to make sure I did follow all of the steps to make sure I had it configured correctly and I do[/i]

Q5 has a log error I don't see

Q6 is about speed

Q7 is an OpenVPN error I don't have

Q8 is an OpenVPN error I don't have

Q9 is about confirming that an incoming port is working

Q10 is an error related to STRICT_PORT_FORWARD (which I have at "no") which I don't have

Q11 is a follow up to Q10

Q12 is about configuring Privoxy which I don't have on

Q13 relates to QNAP and OpenVPN which I don't have

Q14 is a Synology specific question

[b]Q15 is about Port Forwarding and I suspect this may be related to my problem. I have paid ProtonVPN and the wg0 file was set to NAT-PMP, so it's my understanding that port forwarding should be automatic through DelugeVPN, but could I be missing something here?[/b]

Q16 is an AUTH error I'm not seeing

Q17 is a log error I'm not seeing

Q18 is an error with other apps and Privoxy

Q19 is a PIA specific question

Q20 is about setting multiple endpoints

[i]Q21 is about how to use WireGuard instead of OpenVPN but seems to be the same stuff covered in the more current setup guide that I already did[/i]

Q22 is a log error I'm not seeing

Q23 is a log error I'm not seeing

Q24 is about running other containers through the VPN container

[i]Q25 if I'm understanding correctly is about other apps running through the VPN container (i.e. in Q24), which I'm not doing so I don't think this applies to me.[/i]

Q26 is troubleshooting the arrs to communicate with Deluge and Privoxy

Q27 is cumulative from Q24-25

Q28 is about configuring a different endpoint with wireguard

Q29 is an error I'm not seeing

Q30 is an error where you CAN access the webUI on LAN but not outside; but I cant see it on LAN

Q31 is about using Tailscale, which I'm not

~~~

I then followed the instructions (thanks to a user on the Deluge forums) to go here: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

I followed those steps and made the debug log, appended it with the YAML from my settings, and put it on Pastebin here: https://pastebin.com/D11uPf2z

I didn't make the github "issue" because I don't want to be redundantly asking for help when you folks are already helping.

Thank you again for your time!

16 minutes ago, Johnfest said:

Yes I'm using Bridge.

Yes I did that part.

I also went through the entire FAQ here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

In the interest of making sure I didn't miss anything, here's my take on every question there. I italicized the two that I think could be relevant but which I already checked; and I bolded the one that stood out but I'm not sure whether it applies:
Q1 is about Kill Switches and doesn't apply

Q2 is about accessing from OUTSIDE the LAN; but I'm inside

Q3 is about Privoxy which I have turned "off" and I don't think is relevant

[i]Q4 is about the LAN_NETWORK environmental variable and just to make sure I did follow all of the steps to make sure I had it configured correctly and I do[/i]

Q5 has a log error I don't see

Q6 is about speed

Q7 is an OpenVPN error I don't have

Q8 is an OpenVPN error I don't have

Q9 is about confirming that an incoming port is working

Q10 is an error related to STRICT_PORT_FORWARD (which I have at "no") which I don't have

Q11 is a follow up to Q10

Q12 is about configuring Privoxy which I don't have on

Q13 relates to QNAP and OpenVPN which I don't have

Q14 is a Synology specific question

[b]Q15 is about Port Forwarding and I suspect this may be related to my problem. I have paid ProtonVPN and the wg0 file was set to NAT-PMP, so it's my understanding that port forwarding should be automatic through DelugeVPN, but could I be missing something here?[/b]

Q16 is an AUTH error I'm not seeing

Q17 is a log error I'm not seeing

Q18 is an error with other apps and Privoxy

Q19 is a PIA specific question

Q20 is about setting multiple endpoints

[i]Q21 is about how to use WireGuard instead of OpenVPN but seems to be the same stuff covered in the more current setup guide that I already did[/i]

Q22 is a log error I'm not seeing

Q23 is a log error I'm not seeing

Q24 is about running other containers through the VPN container

[i]Q25 if I'm understanding correctly is about other apps running through the VPN container (i.e. in Q24), which I'm not doing so I don't think this applies to me.[/i]

Q26 is troubleshooting the arrs to communicate with Deluge and Privoxy

Q27 is cumulative from Q24-25

Q28 is about configuring a different endpoint with wireguard

Q29 is an error I'm not seeing

Q30 is an error where you CAN access the webUI on LAN but not outside; but I cant see it on LAN

Q31 is about using Tailscale, which I'm not

~~~

I then followed the instructions (thanks to a user on the Deluge forums) to go here: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

I followed those steps and made the debug log, appended it with the YAML from my settings, and put it on Pastebin here: https://pastebin.com/D11uPf2z

I didn't make the github "issue" because I don't want to be redundantly asking for help when you folks are already helping.

Thank you again for your time!

I can't see any reason you shouldn't be able to access the webui. You're using this ip and port right? 192.168.1.24:8112. It seems you have set everything correctly, so it should work. It might be something with port forwarding, but I'm not a protonvpn user, so I have no clue about that. You can try to post an issue on github. Since this is an unRAID-specific support thread, you might get more help relevant to your OS there.