Owner gets 403 privileges error + projects stuck Unhealthy

[dreamsth-com]

I have two Free projects in the same Supabase organization showing Unhealthy, and privileged project endpoints are returning 403 even though the account is Owner.

Affected project:
First Project
Project ref: kpxrmwobjfakdvcsvctu
Region: eu-north-1

What I confirmed:

• My account role is Owner
• I added a second Owner account and the same issue occurs there
• supabase projects list works and shows the project
• supabase link --project-ref kpxrmwobjfakdvcsvctu fails
• Running with --debug shows:

GET https://api.supabase.com/v1/projects/kpxrmwobjfakdvcsvctu

Response:

"Your account does not have the necessary privileges to access this endpoint."

Dashboard issues:

• Failed to load branches
• Edge Functions > Secrets:
  "Failed to retrieve project secrets"
  "Your account does not have the necessary privileges to access this endpoint."
• Project status shows Unhealthy
• Database, PostgREST, Auth, Realtime and Storage show Unhealthy
• Edge Functions shows Healthy

I performed a full Restart Project and waited for recovery, but the status remained Unhealthy.

However, the runtime services themselves appear to work:

Postgres:

select now();

works successfully.

select count(*) from pg_stat_activity;

also works.

PostgREST:

curl -i https://kpxrmwobjfakdvcsvctu.supabase.co/rest/v1/

returns HTTP 401 with UNAUTHORIZED_MISSING_API_KEY, meaning the service is reachable.

Auth:

curl -i https://kpxrmwobjfakdvcsvctu.supabase.co/auth/v1/health

returns HTTP 401 with UNAUTHORIZED_MISSING_API_KEY, meaning Auth is reachable.

Storage:

curl -i https://kpxrmwobjfakdvcsvctu.supabase.co/storage/v1/status

returns HTTP 200.

I also tested a new access token and reauthenticated the CLI. The Management API privilege error remains.

Another Free project in the same organization also shows Unhealthy.

This looks like an organization/control-plane/project metadata or authorization issue rather than an application/database issue.

Is there anything I can do to reset the organization/project authorization state, or does this require intervention from Supabase?

[GaryAustin1]

Try a VPN or another network. Log out and in of dashboard.
As some methods are working I agree it does not seem like a project overload type issue causing the unhealthy but more comm between the dashboard and the management API.
Put a support request in if you have not.

[dreamsth-com]

Thanks. I tested Chrome Incognito and Safari and the issue is the same. I also tested with a second Owner account, and another Free project in the same organization also shows Unhealthy.

I’ve now submitted a Supabase support request with the diagnostics and screenshots. Since the runtime services are reachable but the Management API still returns 403 for Owner accounts, this seems to be a Supabase-side control-plane or authorization issue.

I’ll update this discussion when support replies.

[dreamsth-com]

I contacted Supabase support and they said:

"It may be due to the project's OpenFGA relation being out of sync. We have since synchronized."

Now it works and everything is healthy.