CORs issues

[mysticmainframe]

I have a supabase DB and I have in the URL configuration the correct URLS. My backend CORS.RB file has the correct URLS. I have restarted my DB, backend and the frontend.

[Error] Origin https://hopetreeinvoicing-brian-allisons-projects.vercel.app is not allowed by Access-Control-Allow-Origin. Status code: 404
[Error] Fetch API cannot load https://hbobjupvrrbfgliptuwl.supabase.co/session-check due to access control checks.
[Error] Failed to load resource: Origin https://hopetreeinvoicing-brian-allisons-projects.vercel.app is not allowed by Access-Control-Allow-Origin. Status code: 404 (session-check, line 0)
[Error] Error checking session: – “Load failed”
(anonymous function) (index-Cm4uM1ts.js:67:2074)

fetch(“https://hbobjupvrrbfgliptuwl.supabase.co/auth/v1/token”, {
method: “OPTIONS”,
headers: {
“Origin”: “https://hopetreeinvoicing-brian-allisons-projects.vercel.app”,
“Access-Control-Request-Method”: “POST”,
“Access-Control-Request-Headers”: “Authorization, Content-Type”
}
})
.then(response => console.log(response))
.catch(error => console.error(“CORS Error:”, error));
< Promise {status: “pending”}
[Error] Origin https://hopetreeinvoicing-brian-allisons-projects.vercel.app is not allowed by Access-Control-Allow-Origin. Status code: 200
[Error] Fetch API cannot load https://hbobjupvrrbfgliptuwl.supabase.co/auth/v1/token due to access control checks.
[Error] Failed to load resource: Origin https://hopetreeinvoicing-brian-allisons-projects.vercel.app is not allowed by Access-Control-Allow-Origin. Status code: 200 (token, line 0)
[Error] CORS Error: – TypeError: Load failed
TypeError: Load failed
Console Evaluation (Console Evaluation 1:12)

[system]

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

[bestcodes]

Is your website URL added in the Supabase dashboard?

• Go to the dashboard
• Choose your project
• Go to Authentication in the sidebar
• Check Redirect URLs

Also, going to https://hbobjupvrrbfgliptuwl.supabase.co/session-check, it appears to be an invalid path. Are you sure the configuration is all right (both on client and server)? You could be getting a CORS issue because you are going to the wrong address and the CORS config isn’t applied there.