Fix 502 errors during Fly.io proxy deploys #131

Merged

eblume merged 1 commit from fix/deploy-healthcheck-race into main

2026-02-09 11:07:37 -08:00

Author	SHA1	Message	Date
Erich Blume	b667f21e10	Fix 502 errors during Fly.io proxy deploys The health check returned 200 immediately on nginx start, before Tailscale connected. Fly.io routed traffic to the new machine with a cold proxy cache and no MagicDNS, causing upstream DNS timeouts. Defer the health check by returning 503 until a sentinel file (/tmp/tailscale-ready) is created after Tailscale connects. This keeps the old machine serving traffic during the startup window. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-09 11:06:41 -08:00

Author

SHA1

Message

Date

Erich Blume

b667f21e10

Fix 502 errors during Fly.io proxy deploys

The health check returned 200 immediately on nginx start, before
Tailscale connected. Fly.io routed traffic to the new machine with
a cold proxy cache and no MagicDNS, causing upstream DNS timeouts.

Defer the health check by returning 503 until a sentinel file
(/tmp/tailscale-ready) is created after Tailscale connects. This
keeps the old machine serving traffic during the startup window.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-09 11:06:41 -08:00