Getting 520 and 521 error on branch
Anyone else getting 520 and 521 error code on non-prod branches on supabase?
25 Replies
Please don't shout employees or mods here.
This is a user helping user forum with limited Supabase participation. You are the only mentioning an issue at the moment.
This is a user helping user forum with limited Supabase participation. You are the only mentioning an issue at the moment.
Ok, my bad. Then can some help? This is issue blocking our staging environment and we don't see any status updates on status.supabase.com
Don't know if another user has an idea or not. I don't use branching.
There are a few users here using it.
Is it all of your branches or just one. Was it working and just stopped?
If it was working have you filed a support request?
The error is cloudflare can't reach the server.
just this one branch. it was working this morning at 5:47AM and then stopped. No changes occurred between that time and when it stopped working. We are on supabase.com hosting, not self-hosting, thus it seems to be a supabase issue.
In the main branching discussion no one has ever mentioned 520 or 521...
https://github.com/orgs/supabase/discussions/18937
Can you see status of branches like you can a normal instance?
it is not in healthy status
Can you restart them?
Can you guide me? Not sure how
The main settings page for an instance has the option to restart the instance.
on the supabase.com dashboard?
Yes. General settings. I just don't know if branching lets you see all that for an instance it uses or not.
https://supabase.com/dashboard/project/_/settings/general
It's restarting. hopefully this works. I only saw the restart option on the main branch
You restarted the main instance? But you can see the status of a branch?
You restarted the main instance?Yes, that was the only option.
But you can see the status of a branch?
main branch is healthy
staging branch did not reastart, still unhealthyI assume there is a process to restart/relaunch them somehow. But I've never really even read the docs on them besides the blog post. The big discussion thread got no hits on the word restart.
But the status of that branch instance is your issue which causes the 521 errors.
Yeah, pretty much everywhere I go, the DB showes to be offlint for the branch:
It is. The status shows the whole instance is down for some reason.
It's a bit frustrating that this is not reflected int eh status.supabase.com
It is probably just your single branch instance
It crashed for some reason.
Let me try to upgrade the instance infra, maybe that will force it to restart
You might post on the discussion thread about the status being down and how to restart. I saw an SB dev posting there in the past hour I think.
Otherwise support.
The solution here for a normal instance in that state is restart if that does not work then contact support. So just missing how to do that for a branch instance.
Could be a CLI thing also to do it. Just don't know.
will check, thank you
What's the best say to get in touch with support, any ideas?
Use the support form in feedback tab upper right. Also suggest you ask on the thread that you have status down on a branch and how to restart/resolve.