Gammawolf

Do you know why that list generates mostly x.pvt.site addresses now when the ovpn files from PIA still uses x.privacy.network network? How is it finding/keeping this domain list updated as that discrepancy seems like it would cause an issue? Also as mentioned, turning off strict port forwarding but leaving it selected on PIA also doesn't work, unless selecting PIA inherently uses strict port forwarding anyway?

I turned off STRICT_PORT_FORWARD and there was no change, still not working. I then changed VPN_PROV from pia to custom and it worked as normal. I then reverted STRICT_PORT_FORWARD back to yes and it still worked as normal. Going back to VPN_PROV as pia then makes it not work. Which leads me to believe theres something in this VPN_PROV setting specific to PIA that is making it fail? For now it'll keep it on custom.

Something strange maybe with my install, i've been using this for years and been through various vpn providers in that time. I'm with PIA now, and I used to be able to connect with alot of end points. However that slowly has decreased and now it seems the docker only loads up fully and gives me the webpage (i'm assuming because the VPN isn't up) when connected to the few privacy.network entries in the log. If i use a ovpn file for anything else it fails. Any ideas why? I've use ovpn files with hard coded IPs which doesn't work and also tried changing the ip to what the corresponding link below resolves to and it also doesn't work 2026-09-23 20:02:21,551 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- 2026-09-23 20:02:21,551 DEBG 'start-script' stdout output: [info] ca-montreal.privacy.network [info] cyprus.privacy.network [info] ca-vancouver.privacy.network [info] nl-netherlands-so.privacy.network [info] il-israel-2-pf.privacy.network [info] nl-amsterdam.privacy.network [info] morocco.privacy.network [info] albania.pvt.site [info] algeria.pvt.site [info] andorra.pvt.site [info] argentina.pvt.site [info] armenia.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 etc etc

I'm having a few issues and not sure where else to look.. i've had it working fine and recently have gone through an ISP and router/firewall change. My current situation is i cannot get the VPN to work on my city fibre based connection, over LTE it is working fine. I have both connections configured in sdwan and simply enabling a rule that steers traffic originating from my unraid server to the VPN servers IP over LTE, makes the VPN and client download correctly. Disabling this rule on my firewall so that it takes the default connection (city fibre) results in the docker starting up but items are forever stalled. No changes made to the docker settings between working and not working besides enabling/disabling the rule. The tunnels seem both up and connected as far as i can see through the interfaces although when its not working i get alot of TX dropped. Attached the log when its not working on city fibre. Any help or pointers greatly apprieciated. When running on LTE and working normally sh-5.1# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.3 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:ac:11:00:03 txqueuelen 0 (Ethernet) RX packets 22264 bytes 3781648 (3.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22869 bytes 27389758 (26.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 1004 bytes 145782 (142.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1004 bytes 145782 (142.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.7.2.5 netmask 255.255.255.0 destination 10.7.2.5 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 21061 bytes 1730496 (1.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 39657 bytes 24770884 (23.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 When running on city fibre and not working sh-5.1# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.3 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:ac:11:00:03 txqueuelen 0 (Ethernet) RX packets 926 bytes 270200 (263.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 871 bytes 127203 (124.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 9 bytes 1235 (1.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 9 bytes 1235 (1.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.7.2.5 netmask 255.255.255.0 destination 10.7.2.5 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 723 bytes 161632 (157.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 980 bytes 73342 (71.6 KiB) TX errors 0 dropped 2089 overruns 0 carrier 0 collisions 0 cityfibre log.txt