[Bug]: Google OAuth login fails at Supabase /auth/v1/authorize endpoint before provider redirect

[swarnendu19]

Describe the Bug

Google OAuth sign-in on AContext is failing during the Supabase auth initiation step.
When the Continue with Google flow is triggered from the dashboard login page, the application redirects to the Supabase /auth/v1/authorize endpoint with the expected OAuth parameters (provider, redirect_to, PKCE code_challenge, etc.), but the authorization page itself does not load and the request results in a site can’t be reached error.

This prevents the Google OAuth flow from even reaching Google’s consent screen, so users are blocked before authentication can begin.

To Reproduce

Steps to reproduce the behavior:

1. Open the AContext dashboard login page.
2. Click Continue with Google / Sign in with Google.
3. Observe the redirect to the Supabase auth endpoint:
   https://zzdszdbxsoztirtihcet.supabase.co/auth/v1/authorize?...
4. The browser fails to load the authorization endpoint and shows This site can’t be reached (or equivalent network/unreachable page).

Expected Behavior

Clicking Continue with Google should initiate the OAuth flow successfully by loading the Supabase authorization endpoint, then redirecting the user to Google’s consent/login screen, and finally returning to the configured callback URL:

https://dash.acontext.io/auth/callback

Instead, the flow fails before the OAuth provider handoff occurs.

Code Example

Not applicable from the client side, but the failing auth initiation request looks like this:

https://zzdszdbxsoztirtihcet.supabase.co/auth/v1/authorize?provider=google&redirect_to=https%3A%2F%2Fdash.acontext.io%2Fauth%2Fcallback&code_challenge=mecYn3qAwMeCWoGdO4wqM5nJT58EepwckqoG4Xdma_g&code_challenge_method=s256

Environment

• SDK/Language: Web app / Browser OAuth flow
• SDK Version: N/A
• OS: Windows
• Python Version (if applicable): N/A
• Node Version (if applicable): N/A
• Go Version (if applicable): N/A

Error Message/Stack Trace

Browser error shown after redirecting to the Supabase authorization endpoint:

This site can’t be reached
zzdszdbxsoztirtihcet.supabase.co took too long to respond

Screenshots

If needed, I can attach:

• the browser error page shown after the redirect
• the full OAuth authorization URL generated by the app
• the network request details from DevTools

Additional Context

A few implementation details that may help narrow this down:

• The failure occurs before reaching Google’s OAuth consent screen, so this does not appear to be a Google provider configuration issue at the consent step itself.

• The generated authorization URL includes the expected PKCE parameters (code_challenge and code_challenge_method=s256) and a valid-looking callback:
  https://dash.acontext.io/auth/callback

• The issue appears to be at the Supabase auth endpoint / project auth configuration / project reachability layer, since the browser cannot successfully load the /auth/v1/authorize URL at all.

• If this is environment-specific, it may be worth verifying:

  • Supabase project availability / auth service health
  • Google provider configuration in Supabase Auth
  • allowed redirect URLs for https://dash.acontext.io/auth/callback
  • whether the project reference zzdszdbxsoztirtihcet is still active and correctly mapped to the production auth instance

If helpful, I can also provide the exact timestamp of the failed request and a HAR/network capture from the browser.