Urgent SOS: My Supabase Project Thinks It's 2025/6/1 (SELECT NOW() is a Year Ahead, Breaking API Key Auth with 401s)

[Sajid357404]

Hey Supabase Gods & Community!

I've hit a bizarre and critical wall with my project (ID: sqhytxmfhxfkduhrfoln), and I'm pretty sure I've found the culprit – my project's database server seems to be living in the future!

Here's the Lowdown:

1. When I run SELECT NOW(); in my SQL Editor, it spits out a timestamp from freaking 2025 (like 2025-06-01 XX:XX:XX...). I've got the screenshot to prove this temporal anomaly.
2. Because the server clock is off, all my freshly generated JWTs (especially the anon public key) are getting an iat (issued at) timestamp that's also in 2025. My latest anon key, for example, has an iat like 1748769402 – June 1st, 2025.
3. Naturally, when my Next.js app tries to use these "future-issued" keys, your API rightly tells it to GTFO with a 401 Unauthorized. My app then logs an RLS violation, but the 401 is the real party pooper here, all because the keys aren't "valid yet."
4. Just to be crystal clear, my RLS policies for the anon role are golden. I've tested them directly in the SQL editor (SET ROLE anon; INSERT...), and they work like a charm when the role is properly assumed.

The Damage Report:
This time warp means my app can't make any anonymous API calls. Development is dead in the water until my project rejoins us in 2024.

The Mission (Should You Choose to Accept It):
Can you fine folks at Supabase please take a look at the server hosting my project (sqhytxmfhxfkduhrfoln) and give its system clock a good kick back to the present day? Once SELECT NOW() reflects reality, my API keys should start generating with a proper iat, and the 401s should vanish.

Massive thanks for looking into this urgently! My project's future (and present) depends on it!

Cheers,

[GaryAustin1]

I checked the post number and it seems to be from this year... 2025.

[Sajid357404]

[Sajid357404]

its 25.5.1 not 6

[GaryAustin1]

Not sure if you are being serious or not at this point.

Your now() time looks correct.

If you are having issues it is not the year or date.