Getting "FATAL: Tenant or user not found" after project resume and changing db password
My staging project was paused due to inactivity and then I resumed it.
I'm getting this "FATAL: Tenant or user not found" error when trying to connect (it was working before). I changed the password a couple of times to make sure that it wasn't a credentials problem.
I also tried connecting via DBeaver following this guide https://supabase.com/docs/guides/database/dbeaver. I'm copying the data from the Connect -> Session pooler section (host, port, database and user) in Supabase.
I already checked other related errors, the usual solution is to check the user or host which I already did. I'm thinking that maybe when doing the database resume or password change some user data from PostreSQL got corrupted somehow but I'm no SQL expert so I would really appreciate some help.
4 Replies
What user role are you connecting as?
What connection method are you using (direct or session pooler). The 2nd one requires user.instanceid for the role and I have seen that generate this error if just user is used.
I'm copying the params from the Session pooler section.
Not sure about user role, I'm leaving the "Session role" empty as indicated in the guide.
As long as the username has your real instance id after postgres. that looks like a correct setup.
I tried creating a new project in the same org and it lets me connect correctly. I think that maybe after resume or changing password something broke in my project. Is there any SQL code that I can run to check if everything is ok?