Claude d2d79b4f5f Restart the tunnel services after the hub they live inside ... Both VPN services share the provisioning container's network namespace, and a process holds the namespace it started in. Restarting the hub — which every deploy does, to pick up new code — therefore leaves them listening inside a namespace that no longer exists. Nothing errors. The containers stay up, Caddy's log still reports it is serving on the tunnel address, and connections to that address are simply refused. It looks precisely like a gateway that never worked, which is how it presented on the live server after the first successful start. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-07-27 10:22:19 +02:00
..
lib	feat(deploy): releases you can pin to, and a version that tells the truth	2026-07-26 15:21:38 +02:00
clupilot.env.example	fix(deploy): an answer file with a space in a value killed the install	2026-07-26 18:49:58 +02:00
install-agent.sh	Serve the console inside the tunnel, without publishing the internal network	2026-07-27 10:14:33 +02:00
install.sh	Give the status page its own hostname, and name the right one for Stripe	2026-07-27 08:08:57 +02:00
update-agent.sh	Serve the console inside the tunnel, without publishing the internal network	2026-07-27 10:14:33 +02:00
update.sh	Restart the tunnel services after the hub they live inside	2026-07-27 10:22:19 +02:00