TrueImpulse

Since switching over to next gen PIA servers I have been seeing very slow website DNS resolves when using my browser that has its proxy settings pointed to the Deluge privoxy port. After some trouble shooting I decided to remove all the prefilled PIA DNS addresses from Name_Servers in the Deluge templet and only use the Cloudflare addressed. Doing this resolved me slow resolve issue. Turns out that PIA next gen has a new set of server addresses for it as well, link to them below. https://www.privateinternetaccess.com/helpdesk/kb/articles/next-generation-dns-custom-configuration I added the new PIA DNS addresses to Name_Servers and everything is working normally again. Not sure if I missed this in binhex's instructions somewhere but I suggest that everyone who has moving over to PIA next gen also update the Name_Servers from PIA legacy to PIA nextgen addresses. Still not sure why I get slow resolves when the I have PIA DSN addresses listed in Name_Servers. Dose anyone else have a browser pointed at the privoxy port and seeing very slow site resolves?

Just to confirm, are your speeds in megabits or megabytes. I just download an Ubuntu torrent at between 10-12 megabytes per second which is about 80-100 megabits per second. This is on a one gigabit connection using PIA connected to Canada. Deluge displays speeds in bytes (KiB/s-MiB/s) not bits. If 6-12 MiB/s is what your seeing displayed in the webUI that sounds right.

I get they are moving over to next gen but all their update on their helpdesk site stated they were having problems with port forwarding on legacy servers and where "working to fix the issue". I think its now fair to say they had no intention to fix the issue. PIA is always trying to claim transparency but a move like this really doesn't give me any confidence. I'm sure port forwarding matters to a very small percentage of their customer base but its still a feature of their service that should work.

I've been testing the beta image connecting to PIA Next Gen. While using a browser proxied though the container, getting a response from sites initially is slow, as if the DNS is hanging for a few of seconds. I can see the progress message state "waiting for proxy tunnel" displayed by the browser before the page loads. Happens even on sites that should be cached already. Once the site loads, subfolders and content load fine. I tested on a few servers with the same results.

I have the same results, pulled the test image and connected into Canada, no problems. I see there are far more servers that support port forwarding on Next Gen. Hope this is the solution we've been waiting for. It seams PIA considers it low priority to get port forwarding working again on their legacy servers. Thank you binhex for all your efforts to find a work around to PIA's problems.

For anyone trying to find PIA legacy servers that currently work with port forwarding I can confirm both Berlin and Spain will connect. You may have to allow several retries but once connected they do appear to be stable. I'm on the east coast and these are the closes servers I've been able to connect to.

Hi, Having and issue (not sure if it even is an issue) with looking at the IP address when bashing into the deluge container. When I run the command "curl ifconifg.io" though the deluge terminal I get back a public IPv6 address rather then the IPv4 address from PIA that the container is connected. In the web UI on the bottom right I can see PIA's IP address just not using terminal. The really strange part is that I don't have IPv6 enabled on my router and also have Unraid set to IPv4 only in network settings. Also when I run the same command in for example Radarr's terminal window I get my WAN IPv4 address even though in the Radarr seeings I have proxy enabled though Deluge. If I shut down Deluge anything that I have configured to proxy though it can no longer connect. When I proxy my browser though Deluge and do a IP leak test I get the IP address of the PIA server and no leaks. Again not sure if this is even a problem, just want to make sure I don't have any leak with Deluge or any other docker that is using it as a proxy.

Hello, I'm fairly new to unraid (about 4 months) and love it so far but I'm having a small issue and I hope someone can shed light on it. When sharing a file in Nextcloud using the share via email app it seems that the file is being copied into the docker image before its sent. Unraid kept sending alerts of docker image usage at 95% while the file was being downloaded from my server. The file in question was about 8GB in size. It was also not coming from the Nextcloud share, I have an external storage folder added in Nextcloud and mapped in the docker with config type: Path, Host path: /mnt/user/public and Container path: /public. Hope someone has see this before become I'm lost.