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

Handle database not reachable in a better way #103

Open
JackWilb opened this issue Apr 21, 2021 · 4 comments
Open

Handle database not reachable in a better way #103

JackWilb opened this issue Apr 21, 2021 · 4 comments

Comments

@JackWilb
Copy link
Member

When the database is down, the api breaks and doesn't return any information. We should probably have an error message so it's easier to debug

@waxlamp
Copy link
Collaborator

waxlamp commented Apr 21, 2021

What's the exact error you get?

@JackWilb
Copy link
Member Author

When the EC2 was down, Heroku just showed app not reachable. I didn't check for the status code, but probably a 400/500 error

@JackWilb
Copy link
Member Author

Actually, I just checked the uptime robot and it's HTTP 503 - Service Unavailable

@JackWilb
Copy link
Member Author

Test with new API

@JackWilb JackWilb transferred this issue from multinet-app/multinet-server Feb 22, 2022
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