Skip to content
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

Could not connect to the server. - 502 Bad Gateway #392

Closed
soltmar opened this issue Oct 3, 2023 · 2 comments
Closed

Could not connect to the server. - 502 Bad Gateway #392

soltmar opened this issue Oct 3, 2023 · 2 comments

Comments

@soltmar
Copy link

soltmar commented Oct 3, 2023

Hi there,
Today morning I've started to receive below error:
Could not connect to the server. HTTP/1.1 502 Bad Gateway Server: Caddy Date: Tue, 03 Oct 2023 08:03:24 GMT Content-Length: 0

It was all fine yesterday and I didn't make any changes to my localhost.
I'm not really sure if that 502 comes from my local or is it Expose issue ?
I expect it's an expose issue since my local seems to be completely fine.

@soltmar
Copy link
Author

soltmar commented Oct 3, 2023

It seams that eu-1 server is down. us-1 works fine

@sschlein
Copy link
Member

I am closing this because we also added EU-2 as a failover that you can use – also promising to keep an eye on these issues here in the future 🙈

If you encounter issues with the managed network by us, please send a support email so that we can investigate this quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants