stack/wireguard/wg0.conf.example
tim b55754ee49 Document gluetun unhealthy caused by stale WireGuard endpoint IP
Note re-resolving provider endpoints and PersistentKeepalive when the
tunnel sets up but healthchecks fail with DNS i/o timeouts.
2026-07-22 11:15:35 -07:00

32 lines
1.2 KiB
Text

# Rename YOUR provider's config file to `wg0.conf` and put it in this folder.
# It looks roughly like this:
#
# [Interface]
# PrivateKey = yAnz..................................=
# Address = 10.2.0.2/32
# DNS = 10.2.0.1
#
# [Peer]
# PublicKey = xTIBA5rboUvnH4htodjb6e697QjLERt1NAB4mZqp8Dg=
# PresharedKey = ......................................= # only if present
# AllowedIPs = 0.0.0.0/0
# Endpoint = 185.159.157.12:51820
#
# Two required edits before gluetun accepts it:
#
# 1. Remove any IPv6 addresses from the Address and DNS lines, e.g.
# Address = 10.182.160.190/32, fd7d:76ee:...::/128
# becomes
# Address = 10.182.160.190/32
#
# 2. The Endpoint must be an IP address, not a hostname. If yours says
# 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.