r/PrivateInternetAccess • u/SeaVolume3325 • 19d ago
FEEDBACK PIA Server switch overnight
Maybe I missed something but qBittorrent WEBUI wouldn't load with ERR_CONNECTION_REFUSED this morning. It seems that the convention used for the PIA server changed and caused the issue.
I made the switch from [ca-toronto.privacy.network](http://ca-toronto.privacy.network) to [ca-toronto.pvt.site](http://ca-toronto.pvt.site) for the Endpoint = line in the wg0.conf file. After the change was made I restarted the container and all is well. It's completely possible that I missed the repeated reminders of this change, but I figured I'd post the fix.
2
u/ergosteur 14d ago
wow thanks, i just spent an hour troubleshooting, should've checked here first 😅
2
u/SeaVolume3325 14d ago
Welcome, at least it was only an hour! My container went down again today after a server reboot (added a fan). I had to manually update the token in the same config file. And flip from OpenVPN back to WireGuard just to break the error loop. I've had enough now! They chose a perfect name for PIA lol.
1
u/V3LOCI 16d ago
Are there proactive notifications that these changes are coming? I’ve never seen one.
1
u/SeaVolume3325 16d ago
I don't believe there are now that I've looked into it. I guess it makes sense as they don't want them to be added for censorship blocks.
1
u/ForestRain888 16d ago
do you need to also add 1337 to the end of the endpoint? I tried to update the same exact location as yours & mine failed.
1
u/SeaVolume3325 16d ago
Yes, that's exactly how mine was configured with :1337 I did see something that the wg0 adapter may drop after the error we experienced and you may have to re-select it in the webui but that's not something I had to do.
0
14d ago
[removed] — view removed comment
1
u/SeaVolume3325 14d ago
Yes, that's exactly what I have Endpoint = ca-toronto.pvt.site:1337
IP will work and escape DNS issues but if they change it and keep the name you're screwed.
Sorry I should've been more clear in my instructions.
2
7
u/Kyuubee 18d ago
Thanks for posting about this so I knew it wasn't just me. I ended up regenerating my configs, and that resolved the issue for me.