search

thrnz / docker-wireguard-pia

A Docker container for using Wireguard with PIA.
269 stars 54 forks source link

Could not resolve host: serverlist.piaservers.com #106

Open Hallo-457 opened 4 months ago

Hallo-457 commented 4 months ago

Screenshot (84) Screenshot (83)

like the Issue #105 i have a second docker instance on another machine with the same docker compose and there is evereything working fine even after restart

thrnz commented 4 months ago

Nothing immediately comes to mind, especially if the same compose file is working on another machine.

It might be worth trying with FIREWALL=0 set just to rule out the container actively blocking dns queries. Previously allowing loopback traffic and outgoing udp port 53 was enough for the initial dns queries, though seeing as #105 was fixed by rolling back to an earlier version of Docker engine, I wonder if something might have changed there. If it still doesn't work with the firewall disabled, then it might be something else causing the issue instead.

The 404 is likely unrelated, though it does confirm that its resolving. The full url being retrieved is https://serverlist.piaservers.net/vpninfo/servers/v6

Hallo-457 commented 4 months ago

firewall didnt fix the issue, but caused that the container is healthy, but VPN is still not working

Fetching next-gen PIA server list curl: (6) Could not resolve host: serverlist.piaservers.net curl: (6) Could not resolve host: serverlist.piaservers.net curl: (6) Could not resolve host: serverlist.piaservers.net curl: (6) Could not resolve host: serverlist.piaservers.net curl: (6) Could not resolve host: serverlist.piaservers.net curl: (6) Could not resolve host: serverlist.piaservers.net Error reading signature file /tmp/tmp.lecafJ Failed to verify server list Mon May 6 09:01:54 UTC 2024: Failed to generate WireGuard config Mon May 6 09:01:54 UTC 2024: Fatal error

i didnt update anything the last days.

Hallo-457 commented 4 months ago

i cleared that it associated with this container and now:

Mon May 6 09:13:44 UTC 2024: Generating auth token curl: (6) Could not resolve host: www.privateinternetaccess.com Failed to acquire new auth token. Response: Mon May 6 09:13:50 UTC 2024: Failed to acquire new auth token Mon May 6 09:13:50 UTC 2024: Fatal error

thrnz commented 4 months ago

It might be worth trying running something like nslookup serverlist.piaservers.net and/or wget https://serverlist.piaservers.net/vpninfo/servers/v6 inside the container once it's failed just to rule out another curl specific issue (such as #92).

Apart from that I can't think of any other container specific stuff off the top of my head that might be causing the error.

Cartache commented 3 months ago

Dear,

For your information, I was facing the same issue. I had to modify my compose file to make it work. By adding:

    dns:
      - 1.1.1.1
      - 8.8.8.8
bwscheller commented 3 months ago

I am also having this issue and have only been able to resolve it by rebooting my docker box. Rebooting doesn't always resolve the issue. I have seen it be unable to connect for several days and then have no issues for several weeks.

thrnz commented 2 months ago

Depending on the cause, #110 might offer another workaround as it would remove the need for any dns lookups prior to the WireGuard interface coming up.