Assunto: Todas as requisições autenticadas falham com PGRST303 "JWT issued at future" #53123
Replies: 2 comments
|
Your clock skew read is right, and you can pin it down from your side before support gets to it. PostgREST checks Two quick numbers to add to the ticket: select now(), extract(epoch from now())::bigint as db_epoch;and the const [, p] = session.access_token.split('.')
const { iat } = JSON.parse(atob(p.replace(/-/g, '+').replace(/_/g, '/')))
console.log(iat, Math.floor(Date.now() / 1000))If The Edge Function 401 is probably the same error and not a key problem. The legacy service_role JWT has an |
|
Adding to the diagnosis above — the two numbers support needs are the Decode the jq -R 'split(".") | .[1] | @base64d | fromjson | {iat, exp, role, kid}' <<< "$TOKEN"Then get the host clock from the same project: select now() at time zone 'utc' as db_utc, clock_timestamp() at time zone 'utc' as db_utc_now;If Two adjacent checks while you wait, because they rule in or out your own stack being the cause:
Nothing in your app code can fix this one — the fix is support-side — but the pair of timestamps above is the whole ticket. |
Uh oh!
There was an error while loading. Please reload this page.
Subject: All authenticated requests fail with PGRST303 "JWT issued at future"
Project ref: ztcxrxcgztxbmcwhpryo
Since today (2026-11-08) every request to the Data API made with a user
access token fails with HTTP 401:
{"code":"PGRST303","message":"JWT issued at future"}
and are rejected on the very first request, milliseconds after login.
SUPABASE_SERVICE_ROLE_KEY also gets 401 on every call.
It looks like clock skew between Auth and PostgREST on this project's
instance. No user can log in. Could you check the instance clock / NTP sync?
All reactions