If you can’t connect attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

has anyone managed to succesfully remap port 8080 to something else and have webui come up?

1 hour ago, Ver7o said:

has anyone managed to succesfully remap port 8080 to something else and have webui come up?

Sure, but you have to set the WEBUI_PORT variable, and I think I had to add the same port as a new port to get it to work. Been a while since I did it, but I see I still have it there in the template.

I could swear I did it the same before but some reason it didn't take. Now it did. 😒

Thanks a bunch!

This is what I'm seeing in my qbittorrentvpn log. Is this a PIA issue?

Edited June 10Jun 10 by betaman

15 minutes ago, betaman said:

This is what I'm seeing in my qbittorrentvpn log. Is this a PIA issue?

Tiny log snippets aren’t really useful. You need to attach the entire supervisord log as well as your docker run command to your next post. Be sure to redact any users/passwords.

34 minutes ago, wgstarks said:

Tiny log snippets aren’t really useful. You need to attach the entire supervisord log as well as your docker run command to your next post. Be sure to redact any users/passwords.

Yeah, sorry. I know better...haha

tower-diagnostics-20260610-1600.zip

Your supervisord log is in the appdata folder and you can click on the words docker run (it’s a link) to get info on how to generate the command so you can post it.

Edited June 10Jun 10 by wgstarks

16 hours ago, wgstarks said:

Your supervisord log is in the appdata folder and you can click on the words docker run (it’s a link) to get info on how to generate the command so you can post it.

Isn't the syslog.txt in the tower-diagnostics file I posted the same thing? I'm not aware of another method being required to post logs for issues? Also, how would you anonymize?

8 minutes ago, betaman said:

Isn't the syslog.txt in the tower-diagnostics file I posted the same thing? I'm not aware of another method being required to post logs for issues? Also, how would you anonymize?

No. The supervisord log is only for this container. Also, your docker run command isn’t in diagnostics.

17 hours ago, wgstarks said:

Tiny log snippets aren’t really useful. You need to attach the entire supervisord log as well as your docker run command to your next post. Be sure to redact any users/passwords.

Reading back thru the thread, I think my problem might be in an invalid wireguard config file. I'm using PIA so will try to remember how to generate a new config.

EDIT: It looks like when I upgraded to 7.3 that my wireguard tunnel was deleted.

Edited June 11Jun 11 by betaman

IIRC you’ll need to download it from PIA.

PIA has also recently changed the host names for some of their servers so you may be using an invalid host name.

3 minutes ago, wgstarks said:

No. The supervisord log is only for this container. Also, your docker run command isn’t in diagnostics.

How's this

23 hours ago, wgstarks said:

PIA has also recently changed the host names for some of their servers so you may be using an invalid host name.

I think I am...I was using CA Ontario. When I tried to use SpaceInvaders config app, it hangs on this server but I can generate US East no issue.

EDIT: But the weird thing is my Sabnzbdvpn docker from Binhex works just fine with same config. I think I just need to setup wireguard thru PIA and route all docker containers thru it - instead of using these VPN dockers.

Edited June 12Jun 12 by betaman

The documentation linked in the first post includes instructions how to setup WireGuard using PIA.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q21.

Howdy,

After an update I'm having some issues getting the web UI to load and none of my other docker containers that use the VPN are loading. It seems there's a problem with a table value ID of some sort in the logs. I did run the commands on Q1 of the github documentation to force ip table mangle at it says and rebooted the entire server but I'm still having issues. Thank you for the help.

Docker run

supervisord.log

8 minutes ago, CyrusD said:

After an update I'm having some issues getting the web UI to load and none of my other docker containers that use the VPN are loading.

This looks like your problem-

2026-05-29 10:05:35,372 DEBG 'start-script' stdout output:

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

2026-05-29 10:05:35,601 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

2026-05-29 10:05:35,601 DEBG 'start-script' stdout output:

[info] nl-amsterdam.privacy.network

[info] np-nepal-pf.privacy.network

[info] pe-peru-pf.privacy.network

[info] yerevan.privacy.network

[info] monaco.privacy.network

[info] in.privacy.network

[info] gt-guatemala-pf.privacy.network

[info] uy-uruguay-pf.privacy.network

[info] hk.privacy.network

[info] mongolia.privacy.network

[info] ca-toronto.privacy.network

[info] ca-vancouver.privacy.network

[info] morocco.privacy.network

[info] lu.privacy.network

[info] de-germany-so.privacy.network

[info] kazakhstan.privacy.network

[info] ca-ontario.privacy.network

[info] venezuela.privacy.network

[info] ua.privacy.network

[info] bo-bolivia-pf.privacy.network

[info] cyprus.privacy.network

[info] ec-ecuador-pf.privacy.network

[info] uk-2.privacy.network

[info] srilanka.privacy.network

[info] cambodia.privacy.network

[info] ca-ontario-so.privacy.network

[info] kr-south-korea-pf.privacy.network

[info] liechtenstein.privacy.network

[info] sanjose.privacy.network

[info] austria.privacy.network

[info] nl-netherlands-so.privacy.network

[info] ca-montreal.privacy.network

[info] malta.privacy.network

[info] man.privacy.network

[info] bangladesh.privacy.network

[info] montenegro.privacy.network

[info] ba.privacy.network

[info] macau.privacy.network

[info] panama.privacy.network

[info] vietnam.privacy.network

[info] bahamas.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.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] 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

2026-05-29 10:05:35,602 DEBG 'start-script' stdout output:

[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] 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] 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

PIA has made some recent changes to their server host names. You’ll need to correct it in your OVPN (or WireGuard) file.

2 minutes ago, wgstarks said:

This looks like your problem-

2026-05-29 10:05:35,372 DEBG 'start-script' stdout output:

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

2026-05-29 10:05:35,601 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

2026-05-29 10:05:35,601 DEBG 'start-script' stdout output:

[info] nl-amsterdam.privacy.network

[info] np-nepal-pf.privacy.network

[info] pe-peru-pf.privacy.network

[info] yerevan.privacy.network

[info] monaco.privacy.network

[info] in.privacy.network

[info] gt-guatemala-pf.privacy.network

[info] uy-uruguay-pf.privacy.network

[info] hk.privacy.network

[info] mongolia.privacy.network

[info] ca-toronto.privacy.network

[info] ca-vancouver.privacy.network

[info] morocco.privacy.network

[info] lu.privacy.network

[info] de-germany-so.privacy.network

[info] kazakhstan.privacy.network

[info] ca-ontario.privacy.network

[info] venezuela.privacy.network

[info] ua.privacy.network

[info] bo-bolivia-pf.privacy.network

[info] cyprus.privacy.network

[info] ec-ecuador-pf.privacy.network

[info] uk-2.privacy.network

[info] srilanka.privacy.network

[info] cambodia.privacy.network

[info] ca-ontario-so.privacy.network

[info] kr-south-korea-pf.privacy.network

[info] liechtenstein.privacy.network

[info] sanjose.privacy.network

[info] austria.privacy.network

[info] nl-netherlands-so.privacy.network

[info] ca-montreal.privacy.network

[info] malta.privacy.network

[info] man.privacy.network

[info] bangladesh.privacy.network

[info] montenegro.privacy.network

[info] ba.privacy.network

[info] macau.privacy.network

[info] panama.privacy.network

[info] vietnam.privacy.network

[info] bahamas.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.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] 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

2026-05-29 10:05:35,602 DEBG 'start-script' stdout output:

[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] 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] 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

PIA has made some recent changes to their server host names. You’ll need to correct it in your OVPN (or WireGuard) file.

Thanks for the help. Will report back once I’m home and can make the changes.

2 hours ago, wgstarks said:

This looks like your problem-

2026-05-29 10:05:35,372 DEBG 'start-script' stdout output:

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

2026-05-29 10:05:35,601 DEBG 'start-script' stdout output:

[info] List of PIA endpoints that support port forwarding:-

2026-05-29 10:05:35,601 DEBG 'start-script' stdout output:

[info] nl-amsterdam.privacy.network

[info] np-nepal-pf.privacy.network

[info] pe-peru-pf.privacy.network

[info] yerevan.privacy.network

[info] monaco.privacy.network

[info] in.privacy.network

[info] gt-guatemala-pf.privacy.network

[info] uy-uruguay-pf.privacy.network

[info] hk.privacy.network

[info] mongolia.privacy.network

[info] ca-toronto.privacy.network

[info] ca-vancouver.privacy.network

[info] morocco.privacy.network

[info] lu.privacy.network

[info] de-germany-so.privacy.network

[info] kazakhstan.privacy.network

[info] ca-ontario.privacy.network

[info] venezuela.privacy.network

[info] ua.privacy.network

[info] bo-bolivia-pf.privacy.network

[info] cyprus.privacy.network

[info] ec-ecuador-pf.privacy.network

[info] uk-2.privacy.network

[info] srilanka.privacy.network

[info] cambodia.privacy.network

[info] ca-ontario-so.privacy.network

[info] kr-south-korea-pf.privacy.network

[info] liechtenstein.privacy.network

[info] sanjose.privacy.network

[info] austria.privacy.network

[info] nl-netherlands-so.privacy.network

[info] ca-montreal.privacy.network

[info] malta.privacy.network

[info] man.privacy.network

[info] bangladesh.privacy.network

[info] montenegro.privacy.network

[info] ba.privacy.network

[info] macau.privacy.network

[info] panama.privacy.network

[info] vietnam.privacy.network

[info] bahamas.privacy.network

[info] albania.pvt.site

[info] algeria.pvt.site

[info] andorra.pvt.site

[info] argentina.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] 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

2026-05-29 10:05:35,602 DEBG 'start-script' stdout output:

[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] 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] 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

PIA has made some recent changes to their server host names. You’ll need to correct it in your OVPN (or WireGuard) file.

OK I corrected that, using Austria now. The UI now loads. HOWEVER!

I'm still having issues loading up my other docker containers that use the qBittorrent container VPN. 3 of the 4 do not load. For some reason my 4k instance of radarr will load and seems to work fine. It is using ghcr.io/hotio/radarr repository. My 1080p radarr instance that is not working is using ghcr.io/linuxserver/radarr:latest. Also sonarr and firefox are using linuxserver repositories. Not sure if any of that matters but that's the only difference I can find. I didn't change any configuration other than drop in new PIA cert for Austria and updated the qbittorent docker image to the latest.supervisord.log

New supervisord.log file attached. Thank you for the help so far!

Side note: I did test the 1080p radarr docker by removing the extra parameter "--net=container:qBittorentVPN" and setting the network to bridge, this worked. I was able to load the UI. So this makes me believe something isn't right with the VPN still.

2 minutes ago, CyrusD said:

Side note: I did test the 1080p radarr docker by removing the extra parameter "--net=container:qBittorentVPN" and setting the network to bridge, this worked.

What version of Unraid are you using?

3 hours ago, wgstarks said:

What version of Unraid are you using?

Unraid is version 7.2.0

4 hours ago, CyrusD said:

I'm still having issues loading up my other docker containers that use the qBittorrent container VPN. 3 of the 4 do not load. For some reason my 4k instance of radarr will load and seems to work fine.

Looking at your docker run command I see lots of ports listed in VPN_INPUT_PORTS that I'm not seeing a corresponding port mapping for.

See https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md.

Scroll down to Q24.

On 6/13/2026 at 12:06 PM, wgstarks said:

PIA has made some recent changes to their server host names. You’ll need to correct it in your OVPN (or WireGuard) file.

I ended up just configuring a Wireguard Tunnel to work with PIA per this video and just disabling VPN on my binhex VPN containers (vs installing the non-VPN versions):

Edited June 15Jun 15 by betaman

3 minutes ago, betaman said:

I ended up just configuring a Wireguard Tunnel to work with PIA per this video and just disabling VPN on my binhex VPN containers (vs installing the non-VPN versions):

You didn’t need to use the non vpn version. Just need to correct the name of the server you were connecting to. If your current setup works no point in changing it though.

Just now, wgstarks said:

You didn’t need to use the non vpn version. Just need to correct the name of the server you were connecting to. If your current setup works no point in changing it though.

Well, this is super easy to configure and essentially offers the same benefit as the VPN enabled dockers. I didn't change containers as mentioned, just disabled the built-in VPN and moved all my dockers over to the tunnel network. Anyone just starting out and wanting to put "all" their containers behind a VPN should use the method in the video. It's way simpler now with the advances in the OS and use of Wireguard.