Hi everyone,
I’m running into a Supabase Auth issue that I can’t resolve via the UI, and since this is a free-tier project I’m also posting here to see if others have encountered the same situation or found a workaround.
Context:
- Supabase project is active and accessible
- Database works perfectly (tables readable, queries succeed)
- anon/public key is valid and in use
- auth.users table remains empty
- signUp / auth.signUp() fails immediately with error:
“Project has been deleted”
Important details:
- The project was deleted and recreated earlier during setup
- Database schema was recreated and is working
- This looks like an internal Auth service binding issue rather than a database problem
- JWT key rotation is limited in the UI:
- I can create a standby key
- But there is no “make current / promote / rotate” option
- No Auth → Settings section is available in my UI
- Revoking keys is discouraged because no new key can be promoted to current
Observations:
- Read-only operations work
- Any Auth write operation (signup) fails before creating a user
- Error only appears during auth actions, not during normal DB access
Constraints:
- Free Supabase account
- Support ticket opened, but response time may be long
- Looking for community experience or workaround
Questions:
- Has anyone seen “Project has been deleted” errors on Auth while the project still exists?
- Is there a known workaround for re-binding Auth without deleting the database?
- Any safe way to force Auth to refresh/rebind keys on free tier?
Thanks in advance — any insights are appreciated.