Fix fly-deploy WARNING by starting nginx before Tailscale #128

Merged

eblume merged 1 commit from fix/fly-deploy-warnings into main

2026-02-09 07:01:59 -08:00

Author	SHA1	Message	Date
Erich Blume	0e23adcc71	Fix fly-deploy WARNING by starting nginx before Tailscale The deploy WARNING ("app is not listening on the expected address") was caused by a race: start.sh ran Tailscale setup (~5-10s) before starting nginx, so Fly's post-start socket check found nothing on port 8080. Fix by starting nginx first and deferring upstream DNS resolution to request time via resolver + variable in proxy_pass. DNS results are cached for 30s per worker to avoid per-request lookups. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-09 07:00:19 -08:00

Author

SHA1

Message

Date

Erich Blume

0e23adcc71

Fix fly-deploy WARNING by starting nginx before Tailscale

The deploy WARNING ("app is not listening on the expected address") was
caused by a race: start.sh ran Tailscale setup (~5-10s) before starting
nginx, so Fly's post-start socket check found nothing on port 8080.

Fix by starting nginx first and deferring upstream DNS resolution to
request time via resolver + variable in proxy_pass. DNS results are
cached for 30s per worker to avoid per-request lookups.

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

2026-02-09 07:00:19 -08:00