Files
supabase/apps/docs/content/troubleshooting/forbidden-resource-error-from-the-cli-L6rm6l.mdx
Charis 47705a8968 chore: replace all supabase urls with relative urls (#38537)
* fix: rewrite relative URLs when syncing to GitHub discussion

Relative URLs back to supabse.com won't work in GitHub discussions, so
rewrite them back to absolute URLs starting with https://supabase.com

* fix: replace all supabase urls with relative urls

* chore: add linting for relative urls

* chore: bump linter version

* Prettier

---------

Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
2025-09-09 12:54:33 +00:00

28 lines
1.8 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title = "Forbidden resource error from the CLI"
github_url = "https://github.com/orgs/supabase/discussions/21602"
date_created = "2024-02-27T09:37:38+00:00"
topics = [ "cli", "platform" ]
keywords = [ "cli", "authorization", "token", "permissions" ]
database_id = "b095c3ed-23e7-4a17-9e33-d811af25ba67"
[api]
cli = [ "supabase-link", "supabase-login" ]
[[errors]]
http_status_code = 403
message = "Forbidden resource error"
---
This error typically occurs as a protective measure to prevent unauthorized access to critical operations.
To address this issue, we recommend following these troubleshooting steps:
- Verify Project ID: Ensure the $PROJECT*REF variable in your commands contains the correct Project ID. You can find your Reference ID under [Project -> Settings -> General](/dashboard/project/*/settings/general) in your Supabase Dashboard. A Reference ID looks something like `xvljpkujuwroxcuvossw`.
- Authorization Check: Confirm that youve been properly authorized. You can also generate a new Access Token in your dashboard and use it for login. Generate a new token [here](/dashboard/account/tokens) and use it to [log in](/docs/reference/cli/supabase-login).
- Re-link Project: Try [re-linking](/docs/reference/cli/supabase-link) your project with the newly generated token.
- Owner/Admin Permissions: Make sure you have [Owner/Admin](/docs/guides/platform/access-control) permissions for the project.
- CLI Version: Ensure you are using the latest version of the Supabase CLI. If not, update to the most recent version available at [Supabase CLI GitHub](https://github.com/supabase/cli).
If the issue persists, add a --debug --create-ticket flags to your command and contact [support](/support) with the ticket id and debug logs, which can help in diagnosing the problem further.