-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Troubleshooting upstream errors #1404
Labels
Comments
These docs are ready, but I haven't merged the Troubleshooting / Zero FAQ docs until we decide where these docs should live. See #1426 for more information. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We want to do a new section for docs for upstream errors.
We split the Core pomerium errors to two pages now. All normal errors and Upstream connection errors.
The goal was to have less people contact us when the issue is on there upstream servers side.
Prior art:
https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-521-web-server-is-down
Error codes and descriptions from Envoy:
https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/response_code_details
We are only counting the around 7 codes that have 'upstream' in them.
The text was updated successfully, but these errors were encountered: