ZimaOS "IP n/a" and all traffic stopped

[johnfest]

Hey all,

I'm new to homelabbing and I haven't used Linux in about 20 years, so I'm relearning a lot as I go. I'm just trying to put together a basic media server to demonstrate for the family that we don't need to pay for six streaming services; and assuming that works I'm going to upgrade from there.

I set up using this video https://www.youtube.com/watch?v=Pr7tPDe3Fks and followed every step to get things up and running (skipping the chown steps because I had no preexisting media libraries; and the usenet because I'm only setting up for torrents right now).

I'm on ZimaOS 1.6.2 and Deluge 2.2.0. I'm using Proton VPN on the free tier; I set up with WireGuard.

I was able to download two public domain movies (Night of the Living Dead (1968) and The Last Man On Earth (1964)) and I took a break for dinner. Both films were actively seeding when I walked away.

When I came back, all activity had stopped. I searched for another movie and found it via Prowlarr so I queued it up and it appeared in Deluge. Connections are at 0; Upload and Download are at 0; Protocol Traffic Down/Up is at 0; the field where my external IP had appeared earlier now says "IP n/a"; my storage is connected and correct.

I tried restarting the Gluetun/Deluge container; then stopping it and starting over. I reviewed the settings and they all look the same as when I started them. I tried restarting my entire system through ZimaOS. The issue persists.

I reviewed the FAQ and Troubleshooting pages here. I searched the forums here and searched the web for others having the same problem. I ran

Code: Select all

 curl ipinfo.io 

inside the container terminal and it shows that my VPN is working and I have an external IP in the Netherlands. One person said that they had this problem when they set Preferences to not use a Random Incoming Port, so I checked that, but my setting was already to use random.

Any ideas? Thanks so much in advance for your time and support!

[ambipro]

Gluetun is notoriously difficult to set up, and with proton VPN especially as its port and IP are not persistant. Some VPNs offer dedicated IPs with static port forwarding, Proton is not one of those.

If you only use a VPN with Deluge, I may suggest you look into either hotio or binhex's Docker containers, which support VPNs of both wireguard and openvpn and will automatically update.

It sounds like your VPN connection is being reset, and once it does that Deluge would need to be restarted. If you aren't partial to Gluetun (I don't know anyone who is after trying to use it in cases like this) then even if you're running Docker just for the Deluge container with VPN support, it may be worth it.

[shinger]

Hi John,

You really went for it head first...(homelabbing) and you are more then welcome with any questions that i might help you with .

I don't use Gluetun, prolarr and the rest of those tools as i don't watch any movies/series these days, so ambi kan help you with that.

When it comes to VPN. I myself use hide.me (see the comparison one of the better i must say https://vpn.techlore.tech). I also live in the Netherlands and it works flawlessly using their wireguard tunnel. They support port forwarding. HOWEVER i have changed my infrastructure at home in such a way that i can direct my traffic the way i want. Some goes over their VPN tunnel, while other traffic goes over my normal ISP connection. This might be too technically and scary to even dive in to it, but if you are interested let me know.

In my case i have setup hide.me tunnel with my OpenWRT VirtualMachine (Open Source router OS) running on a Proxmox mini-pc, where all my internet traffic comes in and goes out. That way i don't need to configure any device at home or even when i am outside. When i am outside i simply connect to my own private wireguard tunnel to thise OpenWRT VM and the traffic is led through Pihole (blocking advertisements) and going to the internet over my internet connection at home..ie..hide.me WIreguard VPN tunnel.

In your case you MIGHT have to create your own Docker image with a Docker file or if one is already available use that one. Then direct your download traffic over the VPN tunnel running within the Docker container. The other option is to setup something your self, that includes diving in to iptables and routing, to specifically let download traffic go over it.

[johnfest]

Gluetun is notoriously difficult to set up, and with proton VPN especially as its port and IP are not persistant. Some VPNs offer dedicated IPs with static port forwarding, Proton is not one of those.

If you only use a VPN with Deluge, I may suggest you look into either hotio or binhex's Docker containers, which support VPNs of both wireguard and openvpn and will automatically update.

It sounds like your VPN connection is being reset, and once it does that Deluge would need to be restarted. If you aren't partial to Gluetun (I don't know anyone who is after trying to use it in cases like this) then even if you're running Docker just for the Deluge container with VPN support, it may be worth it.

Thank you so much for your response! If I'm understanding you correctly, I would just run the Docker Compose for one of those two containers and they will run Deluge through my VPN without the added mess of building Gluetun into the container? I see a Qbit container on hotio but not one for Deluge. Do you have any pros/cons between the hotio and binhex options; and relatirely between Qbit and Deluge?

Thanks again for taking the time to help, it means a lot!

[ambipro]

You'll need to configure (binhex in this case, as hotio doesnt do Deluge - but does other clients if you needed them - such as radarr/sonarr, etc) - with your VPN settings. He has extensive documentation on how to do so, and if you are having trouble he's very active on the Unraid forums. I can probably go and find any questions answered there for you or ask them myself if you don't have an account and don't wanna make one.

But yes, compose with his images would work, as long as you set the appropriate environmental variables for openvpn or wireguard.

https://github.com/binhex/arch-delugevpn

[johnfest]

Okay, so I decided to completely start from scratch just in case I screwed something up while following the aforementioned video guide. I formatted my system entirely and reinstalled ZimaOS from scratch.

I purchased the paid ProtonVPN tier.

I followed the binhex/arch-delugevpn instructions, setting the appropriate environmental variables. 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. I get the following error message:

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.

Here's the log:

Code: Select all

delugevpn  | 2026-08-12 16:38:58,095 DEBG fd 11 closed, stopped monitoring  (stderr)>
delugevpn  | 2026-08-12 16:38:58,095 WARN stopped: start-script (terminated by SIGTERM)
delugevpn  | 2026-08-12 16:38:58,095 DEBG received SIGCHLD indicating a child quit
delugevpn  | Created by...
delugevpn  | ___.   .__       .__
delugevpn  | \_ |__ |__| ____ |  |__   ____ ___  ___
delugevpn  |  | __ \|  |/    \|  |  \_/ __ \\  \/  /
delugevpn  |  | \_\ \  |   |  \   Y  \  ___/ >    <
delugevpn  |  |___  /__|___|  /___|  /\___  >__/\_ \
delugevpn  |      \/        \/     \/     \/      \/
delugevpn  |    https://hub.docker.com/u/binhex/
delugevpn  | 
delugevpn  | 2026-08-12 16:39:25.376781 [info] System information: Linux ca19b96c76db 6.18.9 #1 SMP PREEMPT_DYNAMIC Fri Jul  3 05:33:00 UTC 2026 x86_64 GNU/Linux
delugevpn  | 2026-08-12 16:39:25.411173 [info] Application name: 'delugevpn'
delugevpn  | 2026-08-12 16:39:25.431001 [info] Base image release tag: '2025072801'
delugevpn  | 2026-08-12 16:39:25.461429 [info] Output image release tag: '2.2.0-1-04'
delugevpn  | 2026-08-12 16:39:25.504195 [info] PUID defined as '1000'
delugevpn  | 2026-08-12 16:39:25.544491 [info] PGID defined as '1000'
delugevpn  | 2026-08-12 16:39:25.623574 [info] UMASK defined as '000'
delugevpn  | 2026-08-12 16:39:25.644770 [info] Permissions already set for '/config'
delugevpn  | 2026-08-12 16:39:25.675852 [info] Deleting files in /tmp (non recursive)...
delugevpn  | 2026-08-12 16:39:25.702633 [info] VPN_ENABLED defined as 'yes'
delugevpn  | 2026-08-12 16:39:25.724423 [info] VPN_CLIENT defined as 'wireguard'
delugevpn  | 2026-08-12 16:39:25.744781 [info] VPN_PROV defined as 'protonvpn'
delugevpn  | 2026-08-12 16:39:25.773021 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
delugevpn  | 2026-08-12 16:39:25.803347 [info] VPN_REMOTE_SERVER defined as '185.247.68.50'
delugevpn  | 2026-08-12 16:39:25.824050 [info] VPN_REMOTE_PORT defined as '51820'
delugevpn  | 2026-08-12 16:39:25.843016 [info] VPN_DEVICE_TYPE defined as 'wg0'
delugevpn  | 2026-08-12 16:39:25.862382 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
delugevpn  | 2026-08-12 16:39:25.883146 [info] USERSPACE_WIREGUARD defined as 'no'
delugevpn  | 2026-08-12 16:39:25.903688 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
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.
delugevpn  | 2026-08-12 16:39:25.954393 [warn] ip6tables default policies not available, skipping ip6tables drops
delugevpn  | 2026-08-12 16:39:26.138685 [info] LAN_NETWORK defined as '192.168.1.0/24'
delugevpn  | 2026-08-12 16:39:26.163749 [info] LAN_NETWORK exported as '192.168.1.0/24'
delugevpn  | 2026-08-12 16:39:26.184087 [warn] VPN_USER not defined (via -e VPN_USER), assuming authentication via other method
delugevpn  | 2026-08-12 16:39:26.204716 [warn] VPN_PASS not defined (via -e VPN_PASS), assuming authentication via other method
delugevpn  | 2026-08-12 16:39:26.226715 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
delugevpn  | 2026-08-12 16:39:26.246991 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
delugevpn  | 2026-08-12 16:39:26.267563 [info] ENABLE_STARTUP_SCRIPTS not defined (via -e ENABLE_STARTUP_SCRIPTS), defaulting to 'no'
delugevpn  | 2026-08-12 16:39:26.288159 [warn] ENABLE_SOCKS not defined (via -e ENABLE_SOCKS), defaulting to 'no'
delugevpn  | 2026-08-12 16:39:26.308560 [warn] ENABLE_PRIVOXY not defined (via -e ENABLE_PRIVOXY), defaulting to 'no'
delugevpn  | 2026-08-12 16:39:26.329444 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
delugevpn  | 2026-08-12 16:39:26.349936 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
delugevpn  | 2026-08-12 16:39:26.370422 [info] DELUGE_ENABLE_WEBUI_PASSWORD defined as 'yes'
delugevpn  | 2026-08-12 16:39:26.393203 [info] Starting Supervisor...
delugevpn  | 2026-08-12 16:39:26,617 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
delugevpn  | 2026-08-12 16:39:26,618 INFO Set uid to user 0 succeeded
delugevpn  | 2026-08-12 16:39:26,624 INFO RPC interface 'supervisor' initialized
delugevpn  | 2026-08-12 16:39:26,624 CRIT Server 'unix_http_server' running without any HTTP authentication checking
delugevpn  | 2026-08-12 16:39:26,624 INFO supervisord started with pid 6
delugevpn  | 2026-08-12 16:39:27,628 INFO spawned: 'start-script' with pid 258
delugevpn  | 2026-08-12 16:39:27,631 INFO spawned: 'watchdog-script' with pid 259
delugevpn  | 2026-08-12 16:39:27,634 DEBG 'start-script' stdout output:
delugevpn  | [info] VPN is enabled, beginning configuration of VPN
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,634 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
delugevpn  | 2026-08-12 16:39:27,634 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
delugevpn  | 2026-08-12 16:39:27,640 DEBG 'start-script' stdout output:
delugevpn  | [info] Attempting to load iptable_mangle module...
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,641 DEBG 'start-script' stderr output:
delugevpn  | modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/6.18.9
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,641 DEBG 'start-script' stdout output:
delugevpn  | [warn] Unable to load iptable_mangle module using modprobe, trying insmod...
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,643 DEBG 'start-script' stderr output:
delugevpn  | insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,643 DEBG 'start-script' stdout output:
delugevpn  | [warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,643 DEBG 'start-script' stdout output:
delugevpn  | [info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
delugevpn  | [info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,793 DEBG 'start-script' stdout output:
delugevpn  | [info] Adding 192.168.1.0/24 as route via adapter eth0
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,794 DEBG 'start-script' stdout output:
delugevpn  | [info] ip route defined as follows...
delugevpn  | --------------------
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,795 DEBG 'start-script' stdout output:
delugevpn  | default via 172.17.0.1 dev eth0 
delugevpn  | 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 
delugevpn  | 192.168.1.0/24 via 172.17.0.1 dev eth0 
delugevpn  | local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
delugevpn  | local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
delugevpn  | broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
delugevpn  | local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2 
delugevpn  | broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2 
delugevpn  | local ::1 dev lo table local proto kernel metric 0 pref medium
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,795 DEBG 'start-script' stdout output:
delugevpn  | --------------------
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,834 DEBG 'start-script' stdout output:
delugevpn  | [info] iptables defined as follows...
delugevpn  | --------------------
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,835 DEBG 'start-script' stdout output:
delugevpn  | -P INPUT DROP
delugevpn  | -P FORWARD DROP
delugevpn  | -P OUTPUT DROP
delugevpn  | -A INPUT -s 185.247.68.50/32 -i eth0 -j ACCEPT
delugevpn  | -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
delugevpn  | -A INPUT -s 185.247.68.50/32 -i eth0 -j ACCEPT
delugevpn  | -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
delugevpn  | -A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
delugevpn  | -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
delugevpn  | -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
delugevpn  | -A INPUT -i lo -j ACCEPT
delugevpn  | -A INPUT -i wg0 -j ACCEPT
delugevpn  | -A OUTPUT -d 185.247.68.50/32 -o eth0 -j ACCEPT
delugevpn  | -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
delugevpn  | -A OUTPUT -d 185.247.68.50/32 -o eth0 -j ACCEPT
delugevpn  | -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
delugevpn  | -A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
delugevpn  | -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
delugevpn  | -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
delugevpn  | -A OUTPUT -o lo -j ACCEPT
delugevpn  | -A OUTPUT -o wg0 -j ACCEPT
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,836 DEBG 'start-script' stdout output:
delugevpn  | --------------------
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,838 DEBG 'start-script' stdout output:
delugevpn  | [info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,838 DEBG 'start-script' stdout output:
delugevpn  | [info] Attempting to bring WireGuard interface 'down'...
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,844 DEBG 'start-script' stderr output:
delugevpn  | Warning: `/config/wireguard/wg0.conf' is world accessible
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,846 DEBG 'start-script' stderr output:
delugevpn  | wg-quick: `wg0' is not a WireGuard interface
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,846 DEBG 'start-script' stdout output:
delugevpn  | [warn] Failed to bring 'down' WireGuard kernel implementation
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,846 DEBG 'start-script' stdout output:
delugevpn  | [info] Configuring WireGuard...
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,851 DEBG 'start-script' stdout output:
delugevpn  | [info] Attempting to bring WireGuard interface 'up'...
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,856 DEBG 'start-script' stderr output:
delugevpn  | Warning: `/config/wireguard/wg0.conf' is world accessible
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,862 DEBG 'start-script' stderr output:
delugevpn  | [#] ip link add dev wg0 type wireguard
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,873 DEBG 'start-script' stderr output:
delugevpn  | [#] wg setconf wg0 /dev/fd/63
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,874 DEBG 'start-script' stderr output:
delugevpn  | [#] ip -4 address add 10.2.0.2/32 dev wg0
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,881 DEBG 'start-script' stderr output:
delugevpn  | [#] ip link set mtu 1420 up dev wg0
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,888 DEBG 'start-script' stderr output:
delugevpn  | [#] wg set wg0 fwmark 51820
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,889 DEBG 'start-script' stderr output:
delugevpn  | [#] ip -4 rule add not fwmark 51820 table 51820
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,890 DEBG 'start-script' stderr output:
delugevpn  | [#] ip -4 rule add table main suppress_prefixlength 0
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,891 DEBG 'start-script' stderr output:
delugevpn  | [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,894 DEBG 'start-script' stderr output:
delugevpn  | [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,895 DEBG 'start-script' stderr output:
delugevpn  | [#] iptables-restore -n
delugevpn  | 
delugevpn  | 2026-08-12 16:39:27,910 DEBG 'start-script' stderr output:
delugevpn  | [#] '/root/wireguardup.sh'
delugevpn  | 
delugevpn  | 2026-08-12 16:39:33,975 DEBG 'start-script' stdout output:
delugevpn  | [info] Successfully retrieved external IP address 104.234.212.131 from URL 'http://checkip.amazonaws.com'
delugevpn  | 
delugevpn  | 2026-08-12 16:39:33,975 DEBG 'start-script' stdout output:
delugevpn  | [info] Script started to assign incoming port for 'protonvpn'
delugevpn  | 
delugevpn  | 2026-08-12 16:39:33,976 DEBG 'start-script' stdout output:
delugevpn  | [info] Successfully brought Wireguard interface 'up'
delugevpn  | 
delugevpn  | 2026-08-12 16:39:36,000 DEBG 'start-script' stdout output:
delugevpn  | [info] ProtonVPN username '' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...
delugevpn  | [info] Script finished to assign incoming port
delugevpn  | 

I'm no expert, but I'm guessing the "FATAL" error might be part of my problem?

EDIT to add: I tried turning the environmental "VPN_ENABLED" to "no" and Deluge starts fine. I tried changing "USERSPACE_WIREGUARD" to "yes" and the exact same thing happens.

[johnfest]

You'll need to configure (binhex in this case, as hotio doesnt do Deluge - but does other clients if you needed them - such as radarr/sonarr, etc) - with your VPN settings. He has extensive documentation on how to do so, and if you are having trouble he's very active on the Unraid forums. I can probably go and find any questions answered there for you or ask them myself if you don't have an account and don't wanna make one.

But yes, compose with his images would work, as long as you set the appropriate environmental variables for openvpn or wireguard.

https://github.com/binhex/arch-delugevpn

I did also join the Unraid forum and post there, so hopefully the mods are kind and approve my post

[ambipro]

You'll need to configure (binhex in this case, as hotio doesnt do Deluge - but does other clients if you needed them - such as radarr/sonarr, etc) - with your VPN settings. He has extensive documentation on how to do so, and if you are having trouble he's very active on the Unraid forums. I can probably go and find any questions answered there for you or ask them myself if you don't have an account and don't wanna make one.

But yes, compose with his images would work, as long as you set the appropriate environmental variables for openvpn or wireguard.

https://github.com/binhex/arch-delugevpn

I did also join the Unraid forum and post there, so hopefully the mods are kind and approve my post

I've worked with him, he's very active and open to adding things (both linuxserver and binhex images pull from my geoip.dat updates at https://geo.el0.org ) but if you cant get help there, i'd be shocked. They're a great community.

[johnfest]

lol...

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.

Here's the log:

https://www.logpasta.com/paste/1d7f80b8 ... 26befe7d55

Here's the YAML for my settings:

Code: Select all

 services:
  arch-delugevpn:
    cpu_shares: 90
    command: []
    container_name: delugevpn
    deploy:
      resources:
        limits:
          memory: 7.64GB
        reservations: {}
      placement: {}
    entrypoint: null
    environment:
      DELUGE_DAEMON_LOG_LEVEL: info
      DELUGE_ENABLE_WEBUI_PASSWORD: yes
      DELUGE_WEB_LOG_LEVEL: info
      LAN_NETWORK: 192.168.1.0/24
      NAME_SERVERS: 1.1.1.1,1.0.0.1
      PGID: "1000"
      PUID: "1000"
      UMASK: "000"
      USERSPACE_WIREGUARD: no
      VPN_CLIENT: wireguard
      VPN_ENABLED: yes
      VPN_PROV: protonvpn
    image: binhex/arch-delugevpn:latest
    labels:
      icon: https://icon.casaos.io/main/all/arch-delugevpn.png
    network_mode: bridge
    ports:
      - target: 8112
        published: "8112"
        protocol: tcp
      - target: 8118
        published: "8118"
        protocol: tcp
      - target: 9118
        published: "9118"
        protocol: tcp
      - target: 58846
        published: "58846"
        protocol: tcp
      - target: 58946
        published: "58946"
        protocol: tcp
      - target: 58946
        published: "58946"
        protocol: udp
    privileged: true
    restart: unless-stopped
    sysctls:
      net.ipv4.conf.all.src_valid_mark: "1"
    volumes:
      - type: bind
        source: /media/HDD-Storage/apps/docker/deluge/data
        target: /data
      - type: bind
        source: /DATA/AppData/arch-delugevpn/config
        target: /config
      - type: bind
        source: /etc/localtime
        target: /etc/localtime
x-casaos:
  author: self
  category: self
  hostname: 192.168.1.24
  icon: https://icon.casaos.io/main/all/arch-delugevpn.png
  index: /
  is_uncontrolled: false
  main: arch-delugevpn
  port_map: "8112"
  scheme: http
  store_app_id: arch-delugevpn
  title:
    custom: arch-delugevpn
    en_us: arch-delugevpn 

[ambipro]

Have you checked out https://github.com/binhex/documentation ... faq/vpn.md