blah.supabase.co/rest/v1 request failing
See original GitHub issueBug report
Describe the bug
Both on the Supabase dashboard (app.supabase.com) and our apps, requests to instance-id.supabase.co/rest/v1
are failing.
This is happening on both Supabase organizations I am a part of.
To Reproduce
Attempt to send any request to `instance-id.supabase.co/rest/v1.
Expected behavior
I expect requests to the supabase postgrest instance to be successful.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
- OS: MacOS
- Browser (if applies) Firefox
Additional context
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:28 (9 by maintainers)
Top Results From Across the Web
Initializing - Supabase
You can initialize a new Supabase client using the createClient() method. The Supabase client is your entrypoint to the rest of the Supabase...
Read more >Application error: a client-side exception has occurred
Supabase.comDashboard. Javascript Reference v2.0. Application error: a client-side exception has occurred (see the browser console for more information).
Read more >Serverless APIs - Supabase
Let's see how to make a request to the todos table which we created in the first step, using the API URL (...
Read more >pg_graphql v1.0 - Supabase
For example, if any part of a multi-mutation GraphQL request fails, the entire request can roll back to leave the database in a...
Read more >Part Two: Row Level Security | Supabase
Supabase Auth Deep Dive Part Two - Row Level Security. ... You'll notice that both reading and writing now fail with an error...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Another update - Supabase domains have been accepted into the Public Suffix List. Over the next few days, we will be offering an alternate domain for affected users. Everyone affected please reach out to beta@supabase.io referencing this issue and I will set you up the alternate domain right away.
Hi all, the investigation is still ongoing but we have some updates. This was caused by user who signed up to host malicious content on Supabase storage. We took down the content within an hour and blocked the account - it looks like they were a very new GitHub account created specifically for this
We worked closely with our contact at Google to clear the subdomain: https://transparencyreport.google.com/safe-browsing/search?url=supabase.co
We are taking steps to mitigate this: