Supabase Dashboard inaccessible — Failed to fetch api.supabase.com

[odehmarjiha-oss]

Hello Supabase team,

I cannot access my Supabase Dashboard using GitHub login.

I keep getting these errors:

• Failed to fetch permissions: Failed to fetch (api.supabase.com)
• Failed to retrieve account information: Failed to fetch (api.supabase.com)

I have tried different devices, networks, incognito mode, and signing out and back in, but the issue persists.

The Supabase status page says all systems are operational.

My application is working and can access its database, but I cannot access the Dashboard or SQL Editor.

I also tried submitting a support ticket without attachments, but the support form fails with "Unable to upload attachments."

Could you please help me identify and resolve this issue?

Thank you.

[Sagargupta16]

Email support@supabase.com from the email address on the GitHub account you sign in with. Supabase's support policy names that as the route when you cannot reach the dashboard or the ticket form, and it is the same address the dashboard shows under the form as "email us directly". Put the organization name or slug, your project ref, the time it started and the two exact error strings in the mail. Ask them to check the account side, since the project itself keeps working.

The support form fails for the same reason as the dashboard. Both errors are one failed call to api.supabase.com: the dashboard loads your profile and permissions from it, and the attachment step refuses to run when no profile id came back, so "Unable to upload attachments" appears even with no files attached. Retrying the form will not get past it until that API responds for you.

One check worth adding to the mail: open https://api.supabase.com/v1/projects in the browser on one of those devices. Normally it answers at once with a JSON 401 Unauthorized (no token, which is fine). If it hangs, shows a Cloudflare block page or a certificate error instead, api.supabase.com is being blocked somewhere on your path and support can look at that side. status.supabase.com showed all systems operational when I checked, so this is not a wide outage.

[colinmccallion-lang]

To add one thing to check before support replies: "Failed to fetch" with no status code means the browser never got a response, so the request is often blocked on your side rather than refused by Supabase.

• Open DevTools > Network, reload the dashboard and click the red api.supabase.com request. If it shows "(blocked:other)", "ERR_BLOCKED_BY_CLIENT" or a DNS error, an ad blocker, privacy extension, VPN, corporate proxy or DNS filter (Pi-hole, NextDNS, router "security" features) is blocking it.
• Try one browser with no extensions on mobile data (not Wi-Fi), so you're on a different network and DNS. If it works there, the cause is your network or extensions.
• If it fails everywhere, include the exact Network error in your email to support@supabase.com. It points them straight to the account side.