Origin connection errors

When Edgelin cannot reach your backend server, visitors see an error page. This article explains the common causes and how to resolve them.

Error Page

When your origin is unreachable, visitors see a branded error page with the domain name and a description of the issue. The page automatically retries the connection, so if your backend recovers, visitors are served normally without manual intervention.

Common Errors and Solutions

Connection refused Your backend server isn't accepting connections on the expected port. Verify the server is running and listening on port 80 or 443. Check that your firewall allows connections from Edgelin's edge IPs.

Connection timed out / context deadline exceeded Your backend took too long to respond. This usually indicates the server is overloaded or a network issue exists between the edge and your origin. Check server resource usage and network connectivity.

No such host DNS resolution failed for your backend address. If you're using a hostname as your backend (rather than an IP), verify the DNS record exists and resolves correctly.

Connection reset by peer Your backend accepted the connection but then closed it unexpectedly. Check your origin server logs for errors. This can happen when the server crashes mid-request or a firewall terminates the connection.

Automatic Recovery

The error page refreshes automatically every few seconds. Once your backend responds again, visitors are served normally. There's no action needed from you beyond fixing the underlying issue with your origin server.

Monitoring

Enable Origin Monitoring to receive email or webhook notifications when your backend becomes unreachable, rather than discovering issues from visitor reports.