Closed ihatecomputerswithapassion closed 4 years ago
This is due to PIA moving over to their 'nextgen' network which is causing interruptions in their existing network, you will need to try some other endpoints, i know ca-montreal works as im using this one without issue.
ca-montreal worked perfectly, thanks!
Is there any status page one can follow at PIA for this maintenance and do you expect these changes will require some future changes on your side?
Tried CA Montreal but am stuck with the external IP showing in Deluge as N/A - any ideas what we can do here please?
@phil-hudson please do the following and post a link to the log, pastebin or something similar:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
I had the problem as well but it eventually fixed it self, seemed to be indeed due to upgrades happening at PIA. But just recently I started getting different issue, where the vpn would connect but it would get stuck at trying to get a port. The curl seems to fail when I look at the logs:
http://209.222.18.222:2000/?client_id=...
Dooes anyone else experience this well?
CA montreal stopped working, can't find any substitute region that works. Sometimes get it to work after numerous restarts of the container.
Also noticed that Sonarr and Radarr (linuxserver's latest image) fails to import completed downloads even though the tests towards the download client is successful, normally resolves once I've successfully restarted the delugevpn container.
This is also doesn't work for me. Am getting a little worried as the Swiss and Swedin endpoints no longer support port forwarding.
Ended up just changing container to transmission
Sent from my iPhone
On 9 Sep 2020, at 19:06, Ryonez Coruscare notifications@github.com wrote:
This is also doesn't work for me. Am getting a little worried as the Swiss and Swedin endpoints no longer support port forwarding.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
This keeps breaking, currently got DE Berlin going. Will the NEXTGEN network work in this docker image?
I am also working with DE Berlin for now.
Works just fine with port forwarding disabled. Only annoying thing now is that it stops working with Sonarr after a few minutes/hours. Cron job to restart the delugevpn container every 60 min has so far been the easiest workaround.
Support for multi remote endpoints and PIA 'Next-Gen' networks now complete, see Q19 and Q20 for details:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
I'm running into issues where deluge UI is accessible but it has stopped downloading. And after a restart of the container, the UI is no longer accessible.
The last time it happened I resolved it by adding the additional port, thinking that was the end of it. Even though the ovpn file I used at that time didn't even support port forwarding.
But after about 24 hours, it stopped working again and I can't get it resolved. While it works, I can curl from the container, but when it doesn't work I can't resolve a host.
I would assume this is related to the VPN no longer working?
Here's my config:
Here's the logs when I start it up.
I have now tried to use a PIA ovpn file that support port forwarding, testing with DE Berlin at the moment, I'm not getting the VPN to start:
Any help is greatly appreciated.