10/2/2023 0 Comments Nikki hearts povThis issue has been occurring for weeks, even with previous-gen that are reportedly still working with the current port forwarding API (Spain, Iran, Italy). I'm also about to abandon PIA for this exact reason. This sucks, because with unraid, there are a lot of dockers pre-scripted with PIA in mind for port forwarding, which is really, really, really nice. I think the biggest problem with them was the price, the rest was really nice (maybe slightly slower than PIA). I used previously, I may go back to them. Now, I have disabled it altogether and came here to rant about it. Waited 5 minutes, tried to "on/off" it, restarted the browser, couldn't do anything. There is no way to switch the server (if it's broken) or to disconnect. Today, I launched my browser and my PIA browser extension was stuck in a loop trying to connect, preventing me from browsing the web in the meantime. Also, some servers stop working but are still listed, so if you connect to them (for me, the swiss one), then you can't navigate the web. You have to turn it off and on, reboot stuff, instead of it just working. Wireguard is supposedly faster and better, but for now the experience is the opposite. Since the migration, I have frequently had my apps on iPad, on my Pixel and also on the browser extension have trouble to connect. I came here because they are a sponsor of the channel. So even if they fix the previous issue I mentioned, how long until the old gen servers are brought down ? There are threads popping about this in unRaid forums too. So for now, the port forward feature can be considered as non existent.Īlso, while looking at this doc page, what was my surprise when I learned that this port forwarding option would only, for now, be available in the desktop app with the next gen servers, which is basically breaking compatibility with Linux or dockers. It is the one that all scripts for dockers use to retrieve the forwarded port assigned to your VPN session. This URL is official, and mentioned in their doc, so. Switched to another one in the list, but then the URL to get the port was down. What was my surprise when I looked at the logs and saw that the X server was not detected anymore as "Port Forward friendly" (but is still listed as such in the doc.). Since they started the migration, my docker was not doing great (let's leave it at that *wink wink*). In itself, it is a good thing, BUT.įirst, I have some dockers that can automagically detect the assigned Forwarded Port from PIA and use it. The problems have started massively since they started doing a migration to new servers, which now apparently support Wireguard by default. I also cannot advise anyone to go with them at the moment, until they fix the issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |