Sites stay up when an edge node's credentials are rejected
When the control plane rejected an edge node's credentials, the node kept retrying them, and sites it served returned "domain not configured". Nodes now re-authenticate within seconds, and the visitor who triggers recovery still gets their page.
An edge node that had its credentials rejected didn’t notice. It went on sending
the same rejected credentials, and every site that node served answered
domain not configured until the node was restarted by hand. That message
suggested a DNS or setup problem, which it wasn’t.
Three things are different now:
- Nodes re-authenticate on rejection. A node that has its credentials refused discards them and signs in again, recovering in seconds rather than staying down.
- The request that triggers recovery succeeds. The node retries once with its fresh credentials, so the visitor who happened to arrive first gets their page instead of an error.
- Errors say what actually happened. If a node genuinely can’t reach the
control plane, the response is now
503 edge node cannot reach control plane— temporary and retryable — rather than a404that looked like a missing domain. A real misconfiguration still returns404.
Included in edge node v0.0.98.