24 minutes ago, youngnapoleon said:

I tried the binhex/arch-qbittorrentvpn:5.1.2-1-03, but unfortunately it's a no-go. All the other dockers are fine... any ideas?

Attach the supervisord log and docker run command to your next post. Be sure to redact users/passwords.

Hello, my setup was working pretty great for the last year until just recently. I am receiving a warning message in the log for PIA endpoint API currently down, skipping endpoint port forward check. I get this on both my vpn images from binhex for sabnzb and bittorrent. Likely not an issue specifically with these images, but before I go nuclear and have to delete it and recreate everything again, I figured I would ask if anyone else has had these issues. My *arr stack cannot download because the VPN doesn't seem to be connected. I can access the GUI when I shut off VPN-ENABLED flag, but cannot when it's on. I haven't changed any networking. Also just noticed that if I turn off Strict Port Forwarding it also allows me into the GUI. I still cannot successfully test any of my server connections though. They seem to fail with an SSL error.

Edited August 12, 2025Aug 12 by Navigator8672

At some time over the past month or so I have lost access to the webui on unraid. I have the container set up to run through proton vpn and this has been running for a little over a year without issue. When I set VPN_ENABLED=NO, I can gain access to the webui telling me something is wrong with the vpn. I regenerated the certificate using a different proton server and this did not resolve the issue.

I fed the log (attached) into chatGPT and it informed me the issue lies in the proton config file. It claims that Alpine base no longer ships with resolvconf and thus cannot handle the DNS IP being injected from the vpn config file or changes were made to resolvconf which prevent it performing this function.

It's solution is to comment out the proton DNS in the config file and use/replace it into NAME_SERVERS instead. This seems to work but I am not knowledgeable enough to determine if this is the right approach

With the background out of the way, I have 3 questions:
1) is the assessment of the situation by chatGPT correct (changes to Alpine base have broken the ability of resolvconf to inject DNS IP)?
2) is removing proton DNS from the vpn config file safe? I checked for DNS leaks with ipleak torrent check and did not see my home or server IP address in the readout
3) is it ok to remove the default entries in NAME_SERVERS and replace them with the proton DNS from the config file?

supervisord.log

Default port for incoming connections.

Hi y'all,

I've tried searching here but couldn't find anything that answered my questions, if you do, please send me the link.

My issue is I have a website that I visited that requires a different port than the default 6881. Periodically, sometimes every day or a few times a day, I have to go into Settings -> Connection -> Port used for incoming connections to set this to a port other than the default 6881.

The issue is, I think my Unraid restarts the Binhex-qbittorrent docker, either that or something else, but the default port often reverted back to 6881. Sometimes it lasted a few days, sometimes it's daily, I need to go in and change to something other than 6881.

My question is where is the setting to change this to a different port that will hold the value upon restart of the docker.

Thanks!

On 8/17/2025 at 1:09 AM, bobbyt said:

At some time over the past month or so I have lost access to the webui on unraid. I have the container set up to run through proton vpn and this has been running for a little over a year without issue. When I set VPN_ENABLED=NO, I can gain access to the webui telling me something is wrong with the vpn. I regenerated the certificate using a different proton server and this did not resolve the issue.

As someone who just spent today ripping my hair out with the same issue, hopefully this can help someone. As I also had a solid setup for a year until recently. I'm purely a hobbyist so please feel free to correct me.

After resetting credentials on the protonvpn side and updating the docker settings, also download a new configuration file and make sure that is reflected in wg0.conf in your wireguard folder. At time of posting my wireguard configuration on Proton is set to expire in exactly a year, hence the "rock solid setup for a year now". Credentials probably just expired, wireguard wouldn't connect and it resulted in dns issues. Just my take, hopefully it helps.

Is there something blocking outbound communication between qBittorrentVPN and other containers while using container names on the same custom docker network? Other containers can ping qBittorrentVPN but it won't work the other way. Container ip's work normally, but a restart changes the ip and something static would be useful for running scripts inside qBittorrentVPN, like with cross-seed.

First thank you for maintaining this container / app - seems as of last night I can no longer access the web panel without first turning off the VPN enabled flag... looking at the logs it seems to start up the outbound tunnel and I'm guessing fails... if I'm reading this right?

2025-09-10 07:36:42,057 DEBG 'start-script' stdout output:
2025-09-10 07:36:42 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
2025-09-10 07:36:42 TLS Error: TLS handshake failed

2025-09-10 07:36:42,058 DEBG 'start-script' stdout output:
2025-09-10 07:36:42 SIGHUP[soft,tls-error] received, process restarting

supervisord.log Command execution.log

Edited September 10, 2025Sep 10 by widz
add files

18 minutes ago, widz said:

TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

Looks like a bad endpoint, try re-downloading the latest openvpn configuration file from your vpn provider, if that doesn't work then try downloading an openvpn confg file for another geolocation.

17 minutes ago, binhex said:

Looks like a bad endpoint, try re-downloading the latest openvpn configuration file from your vpn provider, if that doesn't work then try downloading an openvpn confg file for another geolocation.

tried a few different locations and all seem to be misbehaving... wonder if it's time to bin off HotSpot Shield....

2025-09-10 08:21:27,486 DEBG 'start-script' stdout output:
2025-09-10 08:21:27 TLS: tls_multi_process: initial untrusted session promoted to trusted

2025-09-10 08:21:27,499 DEBG 'start-script' stdout output:
2025-09-10 08:21:27 Connection reset command was pushed by server ('')

2025-09-10 08:21:27,499 DEBG 'start-script' stdout output:
2025-09-10 08:21:27 SIGHUP[soft,server-pushed-connection-reset] received, process restarting

2025-09-10 08:21:27,499 DEBG 'start-script' stdout output:
2025-09-10 08:21:27 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. 

2025-09-10 08:21:27,501 DEBG 'start-script' stdout output:
2025-09-10 08:21:27 Note: Kernel support for ovpn-dco missing, disabling data channel offload.

Any reason why i would get version not available?

30 minutes ago, r2range said:

Any reason why i would get version not available?

Assume your repo is just set for latest?

1 hour ago, widz said:

Assume your repo is just set for latest?

Yes did not change anything since all the docker containers auto update i just noticed it today.

edit : i open the store and searched it checked the docker after and it was fine now.

Edited September 10, 2025Sep 10 by r2range

How do I install plugins?

I tried a link and a file mount.

Nothing happens, and I can't find anything in the supervised file related to this,

Morning guys,

I rebooted my server last night and now binhex-qbittorrent wont start. Initially I thought it was a change in PIAs endpoints, so downloaded a new .ovpn file, deleted the original in /appdata/binhex-qbittorrent/openvpn, uploaded the new one and tried running again.

It failed to start again, so I looked in the log and see this...

I interpret the log is saying that there is no .ovpn file in /appdata/binhex-qbittorrent/qBittorrent/config/openvpn - this folder doesnt exist, so I created it and copied netherlands.ovpn (downloaded from Private Internet Access today) and still it wont start - showing the same error.

Can anyone offer advice to what I am doing wrong?

Many thanks

Edited September 16, 2025Sep 16 by SliMat

This is probably an easy question, but I can't seem to find an answer:

Is there a way to confirm, other than the "External IP Address detected" in QbittorrentVPN that all torrent traffic is going through the VPN? I do see the correct address in that field, but want to make sure I don't miss anything.

Edit: Found out you can use several IP checking websites to see if your IP address or the VPN address is detected. www.whatismyip.net is one.

Also, I had an issue where all my downloads were failing until I put in "/data/" in the Download folder configuration, even though I specified the correct folder in the Unraid template. Seems like it should just be mapped to "/" but at least it works now.

Edited September 17, 2025Sep 17 by Coolsaber57

I've been pulling my hair out over the past couple of days over this and I think I'm close to the solution but I need some help. In short my qBit client will only ever get 1 peer connected, leading to super slow speeds.

I started this endeavor on trueNAS using binhex qBit image on dockge. Got everything configured, used a PIA node that supported port forwarding (ca_ontario), and yet when testing with ubuntu iso, I could only connect to 1 peer, sometimes 0. At the time I wasn't aware of the status indicator on qbit but I have since learned it likely said 'firewalled'. So to troubleshoot, I tested the standalone qbit client worked on my windows machine both with vpn and without. It works without (after a quick port forward on my router) but not with. So I decided to remove variable and try on windows in a docker container, and no configuration was connecting.

I changed variables one at a time, from trueNAS to unRaid. I briefly tried a different qbit image but have since swapped back to binhex, I even tried Deluge and that worked slightly better but still not great and I realized I made mistakes so I wanted to try qBit again.

Now I am on a different vpn provider. All of these situation have lead to the same/similar result of either not being able to connect or only connecting to 1 peer.
I figure the solution is a port forward somewhere but I cant for the life of me figure out where.

Attaching images and logs of everything, logs are with airVpn but I can repost them with pia if needed.

CommandExecutionAVPN.txt supervisord.log

All trackers show as disabled and wont seed.

I had to recreate my binhex-qbittorrentvpn docker after a massive failure... I ended up deleting the docker and starting from new. I copied the /mnt/cache/appdata/binhex-qbittorrentvpn/qBittorrent/data/BT_backup folder and then imported the .torrent files into the GUI and dint allow them to automatically start downloading... I then forced recheck on all torrents and started them and they all show as stalled uploading / stalled downloading / queued and none are uploading. When I check the trackers they all show as disallowed with "This torrent is private"...

Can anyone help with how to fix this? In the BT_backup folder there are .torrent files and .fastresume files.

Thanks

Is there a suggested health check setting? I'm new to docker health checks in general?

    -e HEALTHCHECK_COMMAND=<command> \
    -e HEALTHCHECK_ACTION=<action> \
    -e HEALTHCHECK_HOSTNAME=<hostname> \

i see that, but there's also a docker compose health check setting, what are other people using for things that need to route through the vpn or privoxy?

Hello,

I am having some issues after increasing the Docker vDisk size. I was using this container for about a month with no real issues. After upgrading my vDisk size, it appears that this container is no longer setting the VPN IP to the IP I provide in my wg0.conf file. It is falling back to the gateway IP and assigning that instead.

I am using ProtonVPN, and have successfully torrented with this config and several others that have been setup in a similar fashion.

I have attached 2 log files.

• Docker Command Execution

• Supervisord.log

Thanks for the help!

supervisordCLEANED.log DockerCommandExec.txt

I recently reinstalled Binhex-qBittorrent docker container but I can't seem to get it working again after install.

I'm getting this for qBittorrent execution log:
The configured network interface is invalid. Interface: "wg0"

I've setup wg0 the exact same way I had it previously - proper settings via Proton, downloaded and moved to the wireguard folder.

I'm getting the following from the console (I don't know if this is an issue):

[INFO] Configuration of incoming port is disabled via argument '-gip|--gluetun-incoming-port' or environment variable 'GLUETUN_INCOMING_PORT', executing remaining arguments '/usr/bin/qbittorrent-nox --webui-port=8080 --profile=/config'...

Any help would be very much appreciated

Thank you

I need to run a custom curl command to update my VPN IP with a private tracker. Is there a "tunnel up" script that I can add that command to? Will it persist between version updates?

Or is there a better way to have this container run a curl command upon VPN connection?

(Apologies if this is a common question. I scanned through the FAQ, but if there is relevant information there I did not see it.)

Hello folks, I've been running my setup pretty much without issue for a couple months. Suddenly I am unable to access the GUI anymore. If I turn off the VPN and Port Forwarding it opens and torrents will download, but, if I leave the VPN on but turn PF off I can access the GUI but torrents remain stalled. Nothing in my setup was changed prior to this. I've tried downloading several OVPN locations from PIA VPN, updating my PIA password and verifying that my subscription is still active. I've even tried switching to wireguard.

Towards the end of my supervisord log it states "PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check" but I can access it on my LAN without an issue. I've attached a portion of my supervisord file. Thanks in advance.

Supervisor File

--------------------

2025-10-08 20:36:26,933 DEBG 'start-script' stdout output:

[debug] VPN remote configuration options as follows...

2025-10-08 20:36:26,933 DEBG 'start-script' stdout output:

[debug] VPN remote server is defined as 'swiss.privacy.network'

[debug] VPN remote port is defined as '1197'

[debug] VPN remote protocol is defined as 'udp'

[debug] VPN remote ip is defined as '158.173.152.239'

2025-10-08 20:36:26,934 DEBG 'start-script' stdout output:

[debug] OpenVPN command line:- /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'pia' --setenv VPN_CLIENT 'openvpn' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_ENABLED 'yes' --setenv VPN_REMOTE_SERVER 'swiss.privacy.network' --setenv APPLICATION 'qbittorrent' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --up /root/openvpnup.sh --up-delay --up-restart --keepalive 10 60 --setenv STRICT_PORT_FORWARD 'yes' --setenv VPN_USER 'p7977503' --setenv VPN_PASS 'SonGoku32' --down /root/openvpndown.sh --disable-occ --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/swiss-aes-256-gcm-udp-dns.ovpn' --remote 158.173.152.239 1197 udp --remote 158.173.152.106 1197 udp --remote 158.173.152.230 1197 udp --remote 172.64.147.163 1197 udp --remote 104.18.40.93 1197 udp --remote 104.18.37.206 1197 udp --remote 172.64.150.50 1197 udp --remote 104.19.240.167 1197 udp --remote 104.18.159.201 1197 udp --remote-random

[info] Starting OpenVPN (non daemonised)...

2025-10-08 20:36:26,942 DEBG 'start-script' stdout output:

2025-10-08 20:36:26 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

2025-10-08 20:36:26 WARNING: file 'credentials.conf' is group or others accessible

2025-10-08 20:36:26 OpenVPN 2.6.14 [git:makepkg/f588592ee6c6323b+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Apr 2 2025

2025-10-08 20:36:26,942 DEBG 'start-script' stdout output:

2025-10-08 20:36:26 library versions: OpenSSL 3.5.1 1 Jul 2025, LZO 2.10

2025-10-08 20:36:26 DCO version: N/A

2025-10-08 20:36:26,942 DEBG 'start-script' stdout output:

2025-10-08 20:36:26 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-10-08 20:36:26,943 DEBG 'start-script' stdout output:

2025-10-08 20:36:26 TCP/UDP: Preserving recently used remote address: [AF_INET]104.18.40.93:1197

2025-10-08 20:36:26 UDPv4 link local: (not bound)

2025-10-08 20:36:26 UDPv4 link remote: [AF_INET]104.18.40.93:1197

2025-10-08 20:37:26,202 DEBG 'start-script' stdout output:

2025-10-08 20:37:26 [UNDEF] Inactivity timeout (--ping-restart), restarting

2025-10-08 20:37:26,202 DEBG 'start-script' stdout output:

2025-10-08 20:37:26 SIGHUP[soft,ping-restart] received, process restarting

2025-10-08 20:37:26,202 DEBG 'start-script' stdout output:

2025-10-08 20:37:26 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

2025-10-08 20:37:26 WARNING: file 'credentials.conf' is group or others accessible

2025-10-08 20:37:26 OpenVPN 2.6.14 [git:makepkg/f588592ee6c6323b+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Apr 2 2025

2025-10-08 20:37:26 library versions: OpenSSL 3.5.1 1 Jul 2025, LZO 2.10

2025-10-08 20:37:26 DCO version: N/A

2025-10-08 20:37:27,203 DEBG 'start-script' stdout output:

2025-10-08 20:37:27 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-10-08 20:37:27,203 DEBG 'start-script' stdout output:

2025-10-08 20:37:27 TCP/UDP: Preserving recently used remote address: [AF_INET]104.18.37.206:1197

2025-10-08 20:37:27 UDPv4 link local: (not bound)

2025-10-08 20:37:27 UDPv4 link remote: [AF_INET]104.18.37.206:1197

2025-10-08 20:38:27,276 DEBG 'start-script' stdout output:

2025-10-08 20:38:27 [UNDEF] Inactivity timeout (--ping-restart), restarting

2025-10-08 20:38:27,276 DEBG 'start-script' stdout output:

2025-10-08 20:38:27 SIGHUP[soft,ping-restart] received, process restarting

2025-10-08 20:38:27,276 DEBG 'start-script' stdout output:

2025-10-08 20:38:27 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

2025-10-08 20:38:27 WARNING: file 'credentials.conf' is group or others accessible

2025-10-08 20:38:27,276 DEBG 'start-script' stdout output:

2025-10-08 20:38:27 OpenVPN 2.6.14 [git:makepkg/f588592ee6c6323b+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Apr 2 2025

2025-10-08 20:38:27 library versions: OpenSSL 3.5.1 1 Jul 2025, LZO 2.10

2025-10-08 20:38:27 DCO version: N/A

2025-10-08 20:38:28,276 DEBG 'start-script' stdout output:

2025-10-08 20:38:28 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-10-08 20:38:28,276 DEBG 'start-script' stdout output:

2025-10-08 20:38:28 TCP/UDP: Preserving recently used remote address: [AF_INET]172.64.150.50:1197

2025-10-08 20:38:28,277 DEBG 'start-script' stdout output:

2025-10-08 20:38:28 UDPv4 link local: (not bound)

2025-10-08 20:38:28 UDPv4 link remote: [AF_INET]172.64.150.50:1197

2025-10-08 20:39:28,952 DEBG 'start-script' stdout output:

2025-10-08 20:39:28 [UNDEF] Inactivity timeout (--ping-restart), restarting

2025-10-08 20:39:28,952 DEBG 'start-script' stdout output:

2025-10-08 20:39:28 SIGHUP[soft,ping-restart] received, process restarting

2025-10-08 20:39:28 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.

2025-10-08 20:39:28,952 DEBG 'start-script' stdout output:

2025-10-08 20:39:28 WARNING: file 'credentials.conf' is group or others accessible

2025-10-08 20:39:28 OpenVPN 2.6.14 [git:makepkg/f588592ee6c6323b+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Apr 2 2025

2025-10-08 20:39:28 library versions: OpenSSL 3.5.1 1 Jul 2025, LZO 2.10

2025-10-08 20:39:28 DCO version: N/A

2025-10-08 20:39:29,952 DEBG 'start-script' stdout output:

2025-10-08 20:39:29 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2025-10-08 20:39:29,953 DEBG 'start-script' stdout output:

2025-10-08 20:39:29 TCP/UDP: Preserving recently used remote address: [AF_INET]158.173.152.106:1197

2025-10-08 20:39:29 UDPv4 link local: (not bound)

2025-10-08 20:39:29 UDPv4 link remote: [AF_INET]158.173.152.106:1197

2025-10-08 20:39:30,572 DEBG 'start-script' stdout output:

2025-10-08 20:39:30 [zurich407] Peer Connection Initiated with [AF_INET]158.173.152.106:1197

2025-10-08 20:39:30,712 DEBG 'start-script' stdout output:

2025-10-08 20:39:30 TUN/TAP device tun0 opened

2025-10-08 20:39:30 net_iface_mtu_set: mtu 1500 for tun0

2025-10-08 20:39:30 net_iface_up: set tun0 up

2025-10-08 20:39:30,712 DEBG 'start-script' stdout output:

2025-10-08 20:39:30 net_addr_v4_add: 10.25.110.24/24 dev tun0

2025-10-08 20:39:30 /root/openvpnup.sh tun0 1500 0 10.25.110.24 255.255.255.0 init

2025-10-08 20:39:30,715 DEBG 'start-script' stdout output:

2025-10-08 20:39:30 Initialization Sequence Completed

2025-10-08 20:39:30,717 DEBG 'start-script' stdout output:

[debug] Waiting for valid VPN gateway IP addresses from tunnel...

[debug] Waiting for valid VPN adapter IP addresses from tunnel...

2025-10-08 20:39:31,723 DEBG 'start-script' stdout output:

[debug] Valid VPN adapter IP from tunnel acquired '10.25.110.24'

2025-10-08 20:39:32,729 DEBG 'start-script' stdout output:

[debug] Valid VPN gateway IP address from tunnel acquired '10.25.110.1'

2025-10-08 20:39:32,730 DEBG 'start-script' stdout output:

[debug] Checking we can resolve name 'www.google.com' to address...

2025-10-08 20:39:32,875 DEBG 'start-script' stdout output:

[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.168.68'

2025-10-08 20:39:33,338 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address 158.173.152.106 from URL 'http://checkip.amazonaws.com'

2025-10-08 20:39:33,338 DEBG 'start-script' stdout output:

[info] Script started to assign incoming port for 'pia'

2025-10-08 20:39:33,338 DEBG 'start-script' stdout output:

[info] Port forwarding is enabled

[info] Checking endpoint 'swiss.privacy.network' is port forward enabled...

2025-10-08 20:39:48,581 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

DockerRun (1).txt

Edited October 9, 2025Oct 9 by JordanClouden
Formatted the log into code and add spoiler, added dockerun

After updating unraid from 6.12.5 to 7.1.4 i could no longer access the qbit web ui from my windows pc if tailscale was turned on (on windows) no mater if im at home on the same lan as unraid is on or away on some other network, exit node did not change anything.

I use the unraid tailscale plugin
Qbittorent uses wireguard protonvpn

I read Q30 https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
so added my tailscale ip to lan_network

That solved the issue.


But to the actual question, what caused it in the first place and is there a better solution?

It worked just fine before having only 192.168.1.0/24
did tailscale or unraid change something to break it?
if they did is there a setting to make it work like before or do i need to add the whole 100.x.x.x tailscale ip range to the lan_network config?

Edit: Seems to be working like normal after restarting tailscale on unraid, odd

Edited October 9, 2025Oct 9 by totedodo
additional note

Hi guys, after an update of the unraid server to 7.1.4 I'm not able to start the docker anymore. I'm using PIA and wireguard.

2025-10-09 11:53:13,356 DEBG 'start-script' stdout output:

--------------------

2025-10-09 11:53:13,359 DEBG 'start-script' stdout output:

[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2025-10-09 11:53:13,359 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

2025-10-09 11:53:13,368 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-10-09 11:53:13,372 DEBG 'start-script' stderr output:

wg-quick: `wg0' is not a WireGuard interface

2025-10-09 11:53:13,372 DEBG 'start-script' stdout output:

[warn] Failed to bring 'down' WireGuard kernel implementation

2025-10-09 11:53:13,372 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2025-10-09 11:53:13,826 DEBG 'start-script' stdout output:

[warn] Failed to download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2025-10-09 11:53:13,826 DEBG 'start-script' stdout output:

[info] Trying to connect to the PIA WireGuard API on 'swiss.privacy.network'...

2025-10-09 11:53:13,925 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2025-10-09 11:53:13,934 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-10-09 11:53:13,942 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2025-10-09 11:53:13,944 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

2025-10-09 11:53:13,944 DEBG 'start-script' stderr output:

Key is not the correct length or format: `null'

Configuration parsing error

2025-10-09 11:53:13,946 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0

2025-10-09 11:53:14,005 DEBG 'start-script' stdout output:

[warn] Failed to bring 'up' WireGuard kernel implementation

2025-10-09 11:53:44,009 DEBG 'start-script' stdout output:

[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2025-10-09 11:53:44,009 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'down'...

2025-10-09 11:53:44,019 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-10-09 11:53:44,022 DEBG 'start-script' stderr output:

wg-quick: `wg0' is not a WireGuard interface

2025-10-09 11:53:44,022 DEBG 'start-script' stdout output:

[warn] Failed to bring 'down' WireGuard kernel implementation

2025-10-09 11:53:44,023 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2025-10-09 11:53:44,542 DEBG 'start-script' stdout output:

[warn] Failed to download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2025-10-09 11:53:44,542 DEBG 'start-script' stdout output:

[info] Trying to connect to the PIA WireGuard API on 'swiss.privacy.network'...

2025-10-09 11:53:44,640 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2025-10-09 11:53:44,649 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-10-09 11:53:44,656 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2025-10-09 11:53:44,658 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

2025-10-09 11:53:44,659 DEBG 'start-script' stderr output:

Key is not the correct length or format: `null'

Configuration parsing error

2025-10-09 11:53:44,661 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0

2025-10-09 11:53:44,725 DEBG 'start-script' stdout output:

[warn] Failed to bring 'up' WireGuard kernel implementation

At some point (due to an update?) my binhex-qbittorrentvpn started giving ERR_CONNECTION_REFUSED when trying to navigate to it. Would anyone be so kind as to point me in the right direction?