-
Notifications
You must be signed in to change notification settings - Fork 872
2 errors: failed to fetch + cannot connect to backend server #130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same Issue here |
1 similar comment
Same Issue here |
Fix1 - Go to Open Supabase dashboard → Settings → API → Data API. 2 - In “Exposed schemas” add basejump 3 - Save it, 4 - run supabase db push 5 - restart backend Seemed to fix it for me |
localhost/:1 Access to fetch at 'http://localhost:8000/api/thread/14b47de4-085b-408c-be62-f6ab1f4f66f0/agent/start' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
intercept-console-error.js:50 [API] Failed to start agent: TypeError: Failed to fetch |
You need to run the supabase thing inside the backend folder |
Console Error
Error: Failed to fetch
src/lib/api.ts (449:28) @ startAgent
startAgent
src/lib/api.ts (449:28)
async handleSubmit
src/app/(dashboard)/dashboard/page.tsx (91:9)
Console Error
Error: Cannot connect to backend server. Please check your internet connection and make sure the backend is running.
src/lib/api.ts (473:13) @ startAgent
startAgent
src/lib/api.ts (473:13)
async handleSubmit
src/app/(dashboard)/dashboard/page.tsx (91:9)
The text was updated successfully, but these errors were encountered: