Project-specific signInWithPassword endpoint returning uncoded HTTP 404

[devcojl-ops]

I am testing signInWithPassword against one confirmed, manually provisioned email/password user in a hosted Supabase project.

Observed:

• official @supabase/supabase-js client reaches /auth/v1/token?grant_type=password
• server-side allowlist passes
• no session is established
• user revalidation is not reached
• AuthApiError is returned with HTTP 404 and no error code
• project URL is origin-only
• publishable key belongs to the same project
• public signup is disabled
• email/password user is confirmed
• a normal invalid-credentials response would usually be HTTP 400
• Auth logs were unavailable in the dashboard during diagnosis
• the project dashboard displayed a technical-issue banner

Environment:

• Next.js 14
• @supabase/ssr 0.7.0
• @supabase/supabase-js 2.75.0
• cookie-based SSR sessions
• no service-role key
• no privileged credentials

Has anyone seen a project-specific uncoded HTTP 404 from the password token endpoint, and is there a project-level Auth repair or health check I should request?

[k1ng-arthur]

I looked into it and the only user who had a similar issue said he fixed it by restarting the Database which i caution has been having some capacity issues recently https://status.supabase.com/ so worth bearing in mind. It could be something related to the instance. Besides this reaching out ot support seems like the next step