chesh

That is where it exists virtually within Deluge. So, your system will find it at /apps/docker/deluge/config, but within Deluge it will see it as /config

Is your LAN subnet 192.168.2.0/24?

Need to add your virtual IP (VPN subnet) to your LAN_NETWORK variable.

If you're using a virtual IP block of IPs when connected to your VPN, do you have that subnet as allowed access in the docker settings?

2020-11-11 17:09:07,155 DEBG 'start-script' stdout output: 2020-11-11 17:09:07 AUTH: Received control message: AUTH_FAILED Relevant part of your logs. Use your PIA website credentials (Q16 in the FAQ https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md) and make sure your password is alpha-numeric and less than 99 characters. Do not use the SOCKS/Proxy generated credentials.

Stupid private trackers w/ client version limitations!

Are you sure you're on the latest version of Deluge? privacy.network servers only work w/ the latest Edit: your repository tag should say: binhex/arch-delugevpn Make sure that is set and then do a force update

You're using the username/password generated for SOCKS connections. Use the username and password you sign into the PIA website with. The generated u/p used to work before they switched to nextgen, now you have to use your actual u/p

You're going to have to use a different docker container then. The old 1.3x version of the Deluge container doesn't support next-gen servers and the old PIA servers were shutdown on 10/31. So, you go current w/ Deluge, or you'll have to switch to be able to connect to PIA and use a client that your trackers support.

See Q19 and Q22 in the FAQ: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Not familiar w/ Portainer, but looking at screenshots, I would think it is in the Container section under the DelugeVPN settings, but I may be way off.

What do you have programmed into Host Path 1 variable in your container settings (should be where /config is located).

See Q19 and Q22 in the FAQ to get up and running: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Tried turning off port forwarding temporarily to see if the makes any difference?

@kkuhle You need to migrate to nextgen. See the FAQ Q19: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

See Q19 in the FAQ to make sure you have the right config files: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Also, use your PIA credentials (what you login with into the PIA site) not any generated credentials you might have made within your account. Generated credentials used to work, but it seems w/ the cutover to nextgen, they're no longer supported.

Did you download the ovpn configuration file for a nextgen server? If not, look at the FAQ Q19 on how to set it up.

You're still using the old servers. Upgrade to nextgen. See the FAQ Q19

Here's the list of what supports port forwarding in the nextgen servers: [info] List of PIA endpoints that support port forwarding:- 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] al.privacy.network [info] ad.privacy.network [info] austria.privacy.network [info] brussels.privacy.network [info] ba.privacy.network 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] sofia.privacy.network [info] czech.privacy.network [info] denmark.privacy.network [info] ee.privacy.network [info] fi.privacy.network [info] france.privacy.network [info] de-berlin.privacy.network [info] de-frankfurt.privacy.network [info] gr.privacy.network [info] hungary.privacy.network [info] is.privacy.network [info] ireland.privacy.network [info] man.privacy.network [info] italy.privacy.network [info] lv.privacy.network [info] liechtenstein.privacy.network [info] lt.privacy.network [info] lu.privacy.network [info] mk.privacy.network [info] malta.privacy.network [info] md.privacy.network [info] monaco.privacy.network [info] montenegro.privacy.network 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] nl-amsterdam.privacy.network [info] no.privacy.network [info] poland.privacy.network [info] pt.privacy.network [info] ro.privacy.network [info] rs.privacy.network [info] sk.privacy.network [info] spain.privacy.network [info] sweden.privacy.network [info] swiss.privacy.network [info] ua.privacy.network [info] uk-london.privacy.network [info] uk-southampton.privacy.network [info] uk-manchester.privacy.network [info] bahamas.privacy.network [info] ca-vancouver.privacy.network [info] ca-ontario.privacy.network [info] ca-toronto.privacy.network [info] ca-montreal.privacy.network [info] greenland.privacy.network [info] mexico.privacy.network [info] panama.privacy.network [info] ar.privacy.network [info] br.privacy.network 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] venezuela.privacy.network [info] yerevan.privacy.network [info] cambodia.privacy.network [info] china.privacy.network [info] cyprus.privacy.network [info] georgia.privacy.network [info] hk.privacy.network [info] in.privacy.network [info] israel.privacy.network [info] japan.privacy.network [info] kazakhstan.privacy.network [info] philippines.privacy.network [info] qatar.privacy.network [info] saudiarabia.privacy.network [info] sg.privacy.network [info] srilanka.privacy.network [info] taiwan.privacy.network [info] tr.privacy.network [info] ae.privacy.network [info] vietnam.privacy.network 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] aus-perth.privacy.network [info] au-sydney.privacy.network [info] aus-melbourne.privacy.network [info] nz.privacy.network [info] dz.privacy.network [info] egypt.privacy.network [info] morocco.privacy.network [info] nigeria.privacy.network [info] za.privacy.network

Your username and password were included in this log. I suggest you go and change them. Also, looking at this log, it's saying authentication failed. I'd make sure you have the right username and password

Have you upgraded to the new servers w/ PIA?

I'd say check the permissions on your credentials.conf file or if you haven't switched to next-gen yet, see the post above yours.

Toggle advanced view in the top right section of the Docker page and then click force update on whichever docker container you'd like to update.

@Merijeek - edit your docker container and change your tag to latest instead of the 1.x branch. Your on a pre 2.0 client

FYI @binhex, all of your More Info links need to be updated. They currently point at https://registry.hub.docker.com/u/binhex/<project> and now need to point at https://registry.hub.docker.com/r/binhex/<project>. Seems that the site has changed the way you get to user projects.