mirror of
https://github.com/netbirdio/netbird.git
synced 2026-08-25 00:51:28 +02:00
3439500cc6
ResolveProxyIP exists to wake the lazy proxy peer, and it retried only curl exit 6 — DNS. The wake-up attempt that arrives before WireGuard has brought the tunnel up fails with exit 7 instead, and that returned immediately: no HTTP response from vast-azalea.netbird.local: exit status 7 (curl: (7) Failed to connect ... after 0 ms) So the one function whose job is to tolerate a not-yet-ready endpoint failed on the readiness state it was written for, one second after the client container reported ready. Retry both exit codes within the same window; anything else would still be failing when the window closed and still fails immediately. Raise the access-log ingest window to 60s for the same reason. The proxy streams each entry with a 10s send timeout of its own, so 30s left barely three attempts of headroom before a test that had already got its 200 was failed for a row still in flight.