Cannot check external IP/contact PIA

[mattboy9921]

I have been trying for a few days to fix this but have come up blank. It seems like my container fails to check the external IP, then fails to get the list of port forwarded PIA servers, then fails to download the PIA json to generate a token.

I have changed nothing about my config for months, and have even gone as far as to delete my entire config directory and start from scratch with new .ovpn files fresh from PIA.

Here is my start command:

docker run \
        --cap-add=NET_ADMIN \
        -p 8112:8112 \
        -p 8118:8118 \
        -p 58846:58846 \
        -p 58946:58946 \
        --name=delugevpn \
        -v /mnt/downloads:/downloads \
        -v /opt/deluge:/config \
        -v /etc/localtime:/etc/localtime:ro \
        -e VPN_ENABLED=yes \
        -e VPN_USER=********** \
        -e VPN_PASS=********** \
        -e VPN_PROV=pia \
        -e VPN_CLIENT=openvpn \
        -e STRICT_PORT_FORWARD=yes \
        -e ENABLE_PRIVOXY=no \
        -e LAN_NETWORK=10.0.0.0/8 \
        -e NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1 \
        -e DELUGE_DAEMON_LOG_LEVEL=debug \
        -e DELUGE_WEB_LOG_LEVEL=debug \
        -e VPN_INPUT_PORTS=8112 \
        -e VPN_OUTPUT_PORTS=5678 \
        -e DEBUG=true \
        -e UMASK=000 \
        -e PUID=1001 \
        -e PGID=1009 \
        binhex/arch-delugevpn

Here is my supervisord.log.

[csreynolds]

I was getting the same error after pull #301

I reverted to ghcr.io/binhex/arch-delugevpn:2.1.1-1-01 (the previous version) and it works fine. Not sure how that change made this happen.

Error line I thought was the problem is below. I could have had the same errors further up in the logs but I didn't scroll far enough up.

DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL https://www.privateinternetaccess.com/gtoken/generateToken
[info] 12 retries left
[info] Retrying in 10 secs...

[mattboy9921]

@csreynolds Thank you for the tip about my gist, I believe I've fixed that.

I reverted to the 2.1.1-1-01 you mentioned and everything seems to be working. The section where it tries to check for an external IP occurs before the section you are referring to. It's almost like DNS or a routing issue is preventing the container from getting to URLs which is likely why it's saying they are offline or cannot be reached.

Hopefully someone can shed some light on this situation? Maybe there's some change to it in the latest release that we are unaware of.

[K3v1n-M]

I am getting the same with Nordvpn as a VPN. Something changed in 2.1.1-1-02 that affects the VPN. I can connect with no VPN but the having issues resolving name with VPN.

[CarterBrehm]

Can confirm, I am using PIA and the latest build of the container was giving me the error above. Reverted to arch-delugevpn:2.1.1-1-01 and everything works fine.

[deanacollins]

If anyone is having this problem in docker on Synology, I had to revert the image as described above but also remove the bridge networking and set it to host. Start the container and let it fail, then move it back to bridge. After that it works fine.

[johnistheman]

I am having the same issue.

I have tried:

1. Reverting to 2.1.1-1-01
2. Trying to use host networking, then revert back to bridged. Not on Synology, but it was worth a try.
3. Changing the server I connect to.
4. Changed from Wireguard to OpenVPN.

[K3v1n-M]

My problem was I changed the Name servers from the default. Recommend you check yours.

[johnistheman]

My problem was I changed the Name servers from the default. Recommend you check yours.

Thanks. This was the problem. I considered testing this the other day, then had found some forum where someone mentioned it as well. Sure enough switching to Google/Cloudflare DNS solved the problem.