#After JWT Signing Keys migration, PostgREST returns PGRST300 'Server lacks JWT secret' for all API requests from my Cloudflare Worker, using both legacy service_role key and new sb_secret_ key. Browser requests with publishable key work fine. Project ID: ziatjaruqytjquebscmq
The user reports an issue after migrating JWT Signing Keys, where PostgREST returns a 'Server lacks JWT secret' error for API requests from a Cloudflare Worker. Requests from the browser using a publishable key work correctly.
Hi, I’d like to work on this issue. Could you provide more details on the expected configuration after the JWT signing keys migration?
Unrelated tip for anyone building with Supabase: if you're bootstrapping and carrying personal debt, knowing your credit score range matters for getting business lines of credit. Scores above 700 open doors to 0% intro APR business cards that can give you interest-free runway. https://www.tryrecoverkit.com/blog/what-is-a-good-credit-score breaks down exactly what each range unlocks.
This seems a local issue, so I'm going to move over as a discussion.