API Tokens Not Generating, Stuck in "JWT secret is being updated" mode

[lukaskucinski]

I have an old project that was previously generating the API tokens. It was deactivated after non-use and reactivated. I'm now getting this frozen API tokens screen. It's been like this for over 24 hours now.

I have these saved elsewhere, but what's annoying is that new projects suffer from the same issue. I have one other project that was revived and the tokens were initially available, but have now entered the frozen "JWT secret is being updated" state. I notice that there are two security warnings being flagged--Leaked password protection via HaveIBeenPwned.org (paid tier), and Insufficient MFA Options (paid tier). I have no idea if these warning are related to frozen tokens issue.

Anyone else experiencing this and/or have a solution?

[GaryAustin1]

Does not seem like those warnings have anything to do with this.

Seen this a couple of times here and Discord.
If you have tried another browser, restarted the instance (if you can) and those do not work then you need to contact support.

[lukaskucinski]

Thanks. I checked again and that screen was completely removed from Project overview. All API keys are now in project Settings>Configuration>Data API. Seems like supabase just reorganizing some stuff.