4 people reported
All time, since Jul 20.
Fresh JWTs rejected by Data API
“GET /rest/v1/profiles?select=role&id=eq.<authenticated-user-id> → HTTP 401, PGRST303: JWT issued at future.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/supabase/issues/8872/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Data API rejects fresh user JWTs as issued at future. Auth sign-in and auth.getUser() succeed, but an immediate PostgREST request returns HTTP 401 despite synchronized clocks.
Is this your bug?
File my report- Where
- Data API
- Error text
PGRST303: JWT issued at future- Platforms
- iOS, Web, Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it blocks them completely.
Original reports4, newest first
- Supabase Auth accepts user JWT (200), but PostgREST rejects the same JWT with PGRST303#51867
- Project affected by ongoing “401 errors due to JWT rejections” incident#49295
- 401 JWT rejections on new project — authenticated requests failing (findseeazzmsdzpxobgt)#49255
- Fresh Supabase Auth JWT rejected by PostgREST: PGRST303 “JWT issued at future”#48123