Supabase•2mo ago

After Pg update new JWT stopped working, legacy as well

None of my user can login now... I was in new JWT for a month without issue, till i updated postgres now everyone is stuck and anything i try fail

10 Replies

MartinOP•2mo ago

when i use rcp i get

{
    "code": "PGRST002",
    "details": null,
    "hint": null,
    "message": "Could not query the database for the schema cache. Retrying."
}

{
    "code": "PGRST002",
    "details": null,
    "hint": null,
    "message": "Could not query the database for the schema cache. Retrying."
}

MartinOP•2mo ago

something odd no version show up in dashboard. And the API is on of course

MartinOP•2mo ago

I try full restart no better, i made ticket support but will not get answer for hours

garyaustin•2mo ago

Check your project home page for status of subsystems. Restart the instance?

MartinOP•2mo ago

I tried to do fast restart or full nothing changed sadly. Status say all good.

garyaustin•2mo ago

Probably have to wait for support then.

MartinOP•2mo ago

for a unknown reason i got pg_temp added in the Extra search path after the update. support answered and told me to remove it and it fixed all. This was not in the setting before and was not added by any person of my team, apparently neither by supabase, WTF

garyaustin•2mo ago

Interesting. Not heard of this before. I'll start watching if this comes up again.

garyaustin•2mo ago

So it was here?

MartinOP•2mo ago

yes

Gaming

Programming

After Pg update new JWT stopped working, legacy as well

Did you find this page helpful?