binhex

from your log:- [warn] PIA endpoint 'us-atlanta.privacy.network' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow [info] Please consider switching to one of the endpoints shown below so either set STRICT_PORT_FORWARD to 'no' or choose one of the dozens of other endpoints shown in your log that do support port forwarding.

please do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

i think i see the issue @PeterB i will do some testing and if it looks good will release a new image with the fix.

it all looks fine to me, i think the only things you could try that are left are:- 1. restart the container 2. restart the host if neither of these resolve the issue then im afraid im out of ideas, at least for now, all ican say is this image def does work so it must be a config issue somewhere.

yep its simplicity itself!, follow Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

hmm that does look like a port forwarding related issue, is the port you have forwarded on your router for udp and tcp?, if not try forwarding both protocols. im using pfsense and have tcp and udp for port 19132 open and have no issues connecting internally or over 3G/4G when out and about (once tweaked minecraft PE of course to allow it).

yes, you will only slow things down when using a proxy over a vpn tunnel, its unnecessary.

thats interesting!, so pia have changed things on their end to prevent socks being used for wireguard/openvpn, that makes sense then, i have enhanced Q16 a little so that hopefully the next person will see my 'Note'.

Honestly, I thought it was always the main log on info. I was never aware of ever being able to use the SOCKS credentials... this images has always been based off the pia website credentials, never the socks credentials, but obviously that is up to pia as to what they do or do not accept, perhaps pia now prevent socks credentials being used for wireguard/openvpn authentication? *shrug*, all i can tell you is main website credentials has been working since this image was created.

yes no see Q4 here:- https://github.com/binhex/documentation/blob/master/docker/faq/delugevpn.md

Q16:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

ive seen a couple of people report this but i have been unable to replicate so unsure as to the cause, you could try another endpoint and see if that helps.

if your kernel is older than 5.6.x then yep you are out of luck and will have to stick to openvpn - or join the dark side and use unraid 🙂

yep thats the problem, you are using a tagged version, you need to drop the tag (the colon and everything after it) in order to download the latest image, this will of course mean you will move onto deluge 2.x

then i can only assume you are not running the latest image, what is set for 'repository' for the container?.