Sweet, I was able to fix it by changing the .opvn file to another location.

Been loving this, using it for years. I restarted all my dockers and now I am getting the following error:

2026-05-17 18:37:02,587 DEBG 'start-script' stdout output:
[warn] Failed to download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
2026-05-17 18:37:02,587 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'ca-ontario.privacy.network'...
2026-05-17 18:37:02,620 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
2026-05-17 18:37:02,650 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard
2026-05-17 18:37:02,654 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63
2026-05-17 18:37:02,656 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error
2026-05-17 18:37:02,660 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0
2026-05-17 18:37:02,741 DEBG 'start-script' stdout output:
[warn] Failed to bring 'up' WireGuard kernel implementation

anybody have any ideas?

7 minutes ago, DocLove said:

Been loving this, using it for years. I restarted all my dockers and now I am getting the following error:

2026-05-17 18:37:02,587 DEBG 'start-script' stdout output:
[warn] Failed to download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
2026-05-17 18:37:02,587 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'ca-ontario.privacy.network'...
2026-05-17 18:37:02,620 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
2026-05-17 18:37:02,650 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard
2026-05-17 18:37:02,654 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63
2026-05-17 18:37:02,656 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error
2026-05-17 18:37:02,660 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0
2026-05-17 18:37:02,741 DEBG 'start-script' stdout output:
[warn] Failed to bring 'up' WireGuard kernel implementation

anybody have any ideas?

See Q29: documentation/docker/faq/vpn.md at master · binhex/documentation · GitHub

Thanks, that pointed me in the right direction, for some reason Unraid was not accessing my vlans correctly. while everything else was working, one Vlan wasn't. rebooting unraid fixed the issue.

appreciate the quick reply.

The Doc.

Hello, I am experiencing a problem with my DelugeVPN app where it will run if VPN is off, but will not run if VPN is on. Additionally, when it runs with VPN off, it does not load any of the torrents I have seeding. These torrent files can be found in the state folder for DelugeVPN, along with fastresume and state files, but they do not load automatically. I am unsure if these issues are related, but they did start at the exact same time.

As far as I'm aware, nothing on my end changed before this happened, although obviously something must have. But the docker app was running just fine one day, then suddenly without my actively changing anything with either software or hardware (no system reset or anything) it just stopped working. I've expereicned this before, but the only other time this happened there was a power outage causing an unexpected reset. Last time, I needed to change the ovpn files, but that doesn't seem to be the issue this time (and last time, the issue of not loading the seeding torrents was not present, only the inability to access with VPN turned on).

I am attaching what I believe is the required information per Binhex documentation on GitHub. If any other information is needed, I will provide it. My tech knowledge level is not bad, but not advanced either; I can follow instructions, but rarely know where to look for things.

Thank you in advance for any help with this!

Command Execution.txt supervisord.log

5 hours ago, Krickis said:

As far as I'm aware, nothing on my end changed before this happened, although obviously something must have.

Looks like the PIA endpoint you are using have dropped support for port forwarding. Pick another endpoint from the list below and redo the OVPN setup.

[info] PIA endpoint 'ca-ontario.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:-

From your supervisord.log:

[info] PIA endpoint 'ca-ontario.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:-
2026-06-17 11:30:12,069 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
2026-06-17 11:30:12,069 DEBG 'start-script' stdout output:
[info] cambodia.privacy.network
[info] np-nepal-pf.privacy.network
[info] panama.privacy.network
[info] cyprus.privacy.network
[info] srilanka.privacy.network
[info] macau.privacy.network
[info] bangladesh.privacy.network
[info] uk-2.privacy.network
[info] ua.privacy.network
[info] in.privacy.network
[info] sanjose.privacy.network
[info] ca-vancouver.privacy.network
[info] monaco.privacy.network
[info] ec-ecuador-pf.privacy.network
[info] pe-peru-pf.privacy.network
[info] bo-bolivia-pf.privacy.network
[info] malta.privacy.network
[info] nl-netherlands-so.privacy.network
[info] ca-toronto.privacy.network
[info] yerevan.privacy.network
[info] montenegro.privacy.network
[info] morocco.privacy.network
[info] venezuela.privacy.network
[info] ba.privacy.network
[info] nl-amsterdam.privacy.network
[info] bahamas.privacy.network
[info] uy-uruguay-pf.privacy.network
[info] vietnam.privacy.network
[info] liechtenstein.privacy.network
[info] de-germany-so.privacy.network
[info] hk.privacy.network
[info] kazakhstan.privacy.network
[info] gt-guatemala-pf.privacy.network
[info] ca-montreal.privacy.network
[info] man.privacy.network
[info] mongolia.privacy.network
[info] albania.pvt.site
[info] algeria.pvt.site
[info] andorra.pvt.site
[info] argentina.pvt.site
[info] austria.pvt.site
[info] au-adelaide.pvt.site
[info] au-brisbane.pvt.site
[info] au-melbourne.pvt.site
[info] au-perth.pvt.site
[info] au-sydney.pvt.site
[info] belgium.pvt.site
[info] brazil.pvt.site
[info] bulgaria.pvt.site
[info] ca-ontario.pvt.site
[info] chile.pvt.site
[info] china.pvt.site
[info] colombia.pvt.site
[info] croatia.pvt.site
[info] czech-republic.pvt.site
[info] de-berlin.pvt.site
[info] de-frankfurt.pvt.site
[info] denmark.pvt.site
[info] egypt.pvt.site
[info] es-madrid.pvt.site
[info] es-valencia.pvt.site
[info] estonia.pvt.site
[info] fi-helsinki.pvt.site
[info] france.pvt.site
[info] georgia.pvt.site
[info] greece.pvt.site
[info] greenland.pvt.site
[info] hungary.pvt.site
[info] iceland.pvt.site
[info] indonesia.pvt.site
[info] ireland.pvt.site
[info] israel.pvt.site
[info] it-milano.pvt.site
[info] jp-tokyo.pvt.site
[info] latvia.pvt.site
[info] lithuania.pvt.site
[info] luxembourg.pvt.site
[info] malaysia.pvt.site
[info] mexico.pvt.site
[info] moldova.pvt.site
[info] new-zealand.pvt.site
[info] nigeria.pvt.site
[info] north-macedonia.pvt.site
[info] norway.pvt.site
[info] philippines.pvt.site
[info] poland.pvt.site
[info] portugal.pvt.site
[info] qatar.pvt.site
[info] romania.pvt.site
[info] saudi-arabia.pvt.site
[info] se-stockholm.pvt.site
[info] serbia.pvt.site
[info] singapore.pvt.site
[info] slovakia.pvt.site
[info] slovenia.pvt.site
[info] south-africa.pvt.site
[info] south-korea.pvt.site
[info] switzerland.pvt.site
[info] taiwan.pvt.site
[info] turkey.pvt.site
[info] uk-london.pvt.site
[info] uk-manchester.pvt.site
[info] uk-southampton.pvt.site
[info] united-arab-emirates.pvt.site

Edited June 17Jun 17 by Jorgen

19 hours ago, Jorgen said:

Looks like the PIA endpoint you are using have dropped support for port forwarding. Pick another endpoint from the list below and redo the OVPN setup.

Oh, awesome! Yeah, did the trick. Still doesn't have the torrents auto-populating. I suppose I can add them back manually, even if it is a hassle, unless someone knows a way to use that fastresume file to just get them all added at once?

Edit: Also while I can now access Deluge on the WebUI, I can no longer seem to access via thin client. Both the WebUI and thin client say they are running version 2.2.0 so I don't think it's a version mismatch issue. I have verified the information in the auth file matches the username and password I'm trying to use for the thin client.

Edit 2: After updating Unraid, the web UI broke again, but I was able to find the issue at that point was Variable: LAN_NETWORK in the settings, where I needed to change it from 1.0/24 to 0.0/24. This fixed not only the web UI but also the thin client connecting. So I'm all set, and I appreciate the help I got here, just wanted to post the experience for anyone finding this with the same issue!

Edited June 21Jun 21 by Krickis