Upgrading Postgres is stuck for over 3 hours. Revert?

I upgraded our project from postgres 15 to 17, it went pretty fast like 15 minutes, but now its been stuck in "backing up" for 3 hours. Our app seems to be working fine BUT users keep getting signed out. Please how can we get help with this?

silentworks•12/11/25, 12:25 PM

Open a ticket with Supabase support about this and add project stuck in backing up as the title. https://supabase.com/dashboard/support/new

JensOP•12/11/25, 12:27 PM

Just submitted, but didn't add project stuck. We just upgraded to Team plan to get some help on this. Can explain why users are getting logged out? Everything else seems to be working

JJens Just submitted, but didn't add project stuck. We just upgraded to Team plan to g...

silentworks•12/11/25, 12:28 PM

Not enough detail from you to know why they could be getting logged out. Was this happening before the upgrade? or only since you initiated the upgrade?

Ssilentworks Not enough detail from you to know why they could be getting logged out. Was thi...

JensOP•12/11/25, 12:31 PM

The actual upgrade went pretty fast, then it went into "backing up". When it unpaused I could use all our apps and services. But after a while, both my web and iOS we users got signed out, which happens on bad token. So my guess is something is happening in the upgrade/backup state where user tokens are getting messed up.

JensOP•12/11/25, 12:32 PM

Since the dashboard is unusable I can't share any logs

JensOP•12/11/25, 12:33 PM

Is there anyway to cancel the backup or upgrade? Pretty sure it's stuck, shouldn't take this long for a backup

JJens The actual upgrade went pretty fast, then it went into "backing up". When it unp...

silentworks•12/11/25, 12:33 PM

Yeah probably. Send over your ticket number here and let me see if I can get it escalated since you are now on the Team plan.

JensOP•12/11/25, 12:33 PM

SU-302724

JJens Is there anyway to cancel the backup or upgrade? Pretty sure it's stuck, shouldn...

silentworks•12/11/25, 12:33 PM

You won't be able to, but someone from Supabase would be able to look into it.

Ssilentworks You won't be able to, but someone from Supabase would be able to look into it.

JensOP•12/11/25, 12:37 PM

Can I speak to support somehow?

JJens Can I speak to support somehow?

silentworks•12/11/25, 12:37 PM

Only through the ticketing system that you've already submitted a ticket to.

JensOP•12/11/25, 12:40 PM

Ok, this is very urgent, the app is now unresponsive. Been stuck like this for 4 hours. Please what can we do?

JJens Ok, this is very urgent, the app is now unresponsive. Been stuck like this for 4...

silentworks•12/11/25, 12:41 PM

Wait on support. And I've already pushed it to the back channel we have with Supabase.

Ssilentworks Wait on support. And I've already pushed it to the back channel we have with Sup...

JensOP•12/11/25, 12:41 PM

great, thank you

JensOP•12/11/25, 1:34 PM

Oh I see the error now

 ERROR  [AuthApiError: missing destination name scopes in *models.Session]

 ERROR  [AuthApiError: missing destination name scopes in *models.Session]

This is why users are getting signed out. What is this and can it be fixed?

JJens Oh I see the error now ` ERROR [AuthApiError: missing destination name scopes i...

silentworks•12/11/25, 1:35 PM

Just restarting your project from the dashboard project settings normally resolves this https://supabase.com/dashboard/project/_/settings/general

JensOP•12/11/25, 1:35 PM

I can't do anything!

JensOP•12/11/25, 1:36 PM

Support has replied to ticket, but no help yet, escalated to infra team apparently

JJens I can't do anything!

silentworks•12/11/25, 1:36 PM

I thought that has finished hence why you are seeing the error.

JensOP•12/11/25, 1:36 PM

app/api has been working the whole time (minus first 15 minutes)

JensOP•12/11/25, 1:36 PM

So you are saying once this all finishes, that error will go away?

JensOP•12/11/25, 1:37 PM

hate feeling this helpless...

silentworks•12/11/25, 1:37 PM

Can you try opening your project dashboard in a different browser? also try with a VPN. Just want to rule out that it's not a frontend state that is stuck.

JensOP•12/11/25, 1:39 PM

Tried incognito, same

JJens Tried incognito, same

silentworks•12/11/25, 1:39 PM

No it would need to be a different browser, not the same browser. So if you are using chrome, you would try in firefox

JensOP•12/11/25, 1:40 PM

same in firefox

JensOP•12/11/25, 1:41 PM

JensOP•12/11/25, 1:41 PM

Can you restart the project manually?

JensOP•12/11/25, 1:42 PM

I'm in!

JJens Can you restart the project manually?

silentworks•12/11/25, 1:43 PM

No I'm not a Supabase staff. They've also escalated it to the infra team who will be the ones to get this resolved if it's truely stuck in the upgrade process.

JJens I'm in!

silentworks•12/11/25, 1:44 PM

Is it working now?

JensOP•12/11/25, 1:44 PM

JensOP•12/11/25, 1:44 PM

I'm still seeing these errors. You're saying I should restart project?

JJens I'm still seeing these errors. You're saying I should restart project?

silentworks•12/11/25, 1:45 PM

Yeah restarting the project is what have fixed this for others who had this same issue on here.

JensOP•12/11/25, 1:46 PM

not sure I dare to touch it if it's this fragile

JensOP•12/11/25, 1:46 PM

is it fast?

garyaustin•12/11/25, 1:47 PM

After an upgrade from 15 to 17 it appears some user's auth server is not at the right release for the Postgres version's migrations. Restart fixes that.

If you are down does it matter how fast?

JensOP•12/11/25, 1:49 PM

we are not down, just people getting signed out

JensOP•12/11/25, 1:49 PM

ok let me restart

JensOP•12/11/25, 1:54 PM

I restarted, but it's still happening. We did upgrade from 15 to 17. Kicking users out like this is really bad. Any other suggestions?

garyaustin•12/11/25, 1:55 PM

Are you still getting the missing scope errors?

garyaustin•12/11/25, 1:55 PM

You restarted the DB or the Project?

Ggaryaustin You restarted the DB or the Project?

JensOP•12/11/25, 1:55 PM

the project

JensOP•12/11/25, 1:56 PM

message.txt3.52KB

garyaustin•12/11/25, 1:57 PM

Restarting Project has cleaned up the missing destination in scope errors for everyone else.

No other ideas as that is auth error complaining the auth schema does not match what it's version expects.

garyaustin•12/11/25, 1:58 PM

Wonder if your database upgrade did not finish and so the migrations did not run...

JensOP•12/11/25, 1:58 PM

Can I check somehow?

JensOP•12/11/25, 1:58 PM

(super thankful for all help)

garyaustin•12/11/25, 2:00 PM

Sorry I don't know how to know where a upgrade would log things or mark its status.
There is this log, but have never looked at it.

garyaustin•12/11/25, 2:00 PM

I would also update your ticket to make sure they know you are running but get the specific error.

Upgrading Postgres is stuck for over 3 hours. Revert?

Similar Threads

Similar Threads

Similar Threads