Replies: 2 comments
|
5xx errors are usually internal errors but not always upstream errrors. Sometimes it could be something like Data Api not enabled. You would need to check the actual error message to see if it offers more details. What is the state of your project now, paused or unpaused? You can try doing queries using curl if you don't want to use your frontend client https://supabase.com/dashboard/project/_/integrations/data_api/docs. |
0 replies
|
Same symptoms here since ~09:42 UTC today, eu-central-1 (Free): /auth/v1/health and REST return 521, PostgREST/Auth never start after restart, pause fails with "Failed to verify backup status before pausing". Support ticket open. #53208 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Supabase Community,
I need help troubleshooting persistent API connection issues with my Supabase project.
Project details:
Problem:
I have been unable to establish a reliable connection between my web application and Supabase.
I have encountered the following HTTP errors in the Supabase logs:
/rest-admin/v1/ready/rest-admin/v1/ready/auth/v1/healthSome requests also returned HTTP 200.
The Supabase dashboard previously showed the project status as Healthy, but the API connection problem persisted.
I also received a dashboard notification about technical issues being investigated.
I restored the project after it was automatically paused due to inactivity. The restoration completed successfully, but the connection issue remained. The project was subsequently paused again due to inactivity.
Support history:
I previously submitted a support ticket (SU-497713), but I have not received a specific technical resolution.
My questions:
I would appreciate any guidance. I am trying to resolve this issue without migrating to another backend service unnecessarily.
Thank you for your help.
All reactions