tim/stack
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document gluetun unhealthy caused by stale WireGuard endpoint IP

Browse source 
Note re-resolving provider endpoints and PersistentKeepalive when the
tunnel sets up but healthchecks fail with DNS i/o timeouts.
This commit is contained in:
tim 2026-07-22 11:15:35 -07:00
parent 90f3cf62c5
commit b55754ee49
2 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
wireguard/wg0.conf.example
View file

@ -23,5 +23,10 @@
# something like `Endpoint = se3.vpn.example.org:51820`, resolve it first:
# dig +short se3.vpn.example.org
# and paste the IP back into the file.
# Re-check if gluetun goes unhealthy with "i/o timeout" — provider DNS
# may have moved to a new IP (common with multi-A hostnames).
#
# 3. Optional but recommended behind NAT:
# PersistentKeepalive = 25
#
# Keep AllowedIPs = 0.0.0.0/0 as-is; gluetun handles the routing itself.