Hi I've been working on a project for a few weeks with the React Client SDK and OAuth2.0 Google login. All has been working alright, but today I've started getting some CORS errors , with a weird error related to different localhost ports in the request and the response from the server.
The calls to the appwrite Database don't fail. Only the calls to the Storage bucket fail with this CORS error. This is very strange because the app has been working until now from localhost and I cannot really identify something in my setup that would trigger this.
Many thanks. Let me know if you need additional details for diagnosing.
Browser: Brave 1.81.131 (Official Build) (arm64) / Chromium: 139.0.7258.66 (MacOS) node_modules/appwrite : "version": "18.2.0" npm 10.9.2 node v23.5.0 VITE v7.0.0
Access to fetch at 'https://fra.cloud.appwrite.io/v1/storage/buckets/<REDACTED>/files/<REDACTED>/download?project=<REDACTED>' from origin 'http://localhost:5173' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'http://localhost:5174' that is not equal to the supplied origin. Have the server send the header with a valid value.
Hmmmm it worked when using Chrome. This is very weird.
That said - why would the server return a different port?
Recommended threads
- Not getting data
IDK what the issue is but I am stuck at a weried but that I am calling this function ``` @override Future<List<CategoryModel>> getCategories() async { t...
- Problem with the new Email policies
when user set those thing from cloud panel and when they open that page again or reload that time it forget what we have checked and it set default to false on ...
- Deleted my account, trying to signup aga...
https://cloud.appwrite.io/console/login?error=%7B%22message%22%3A%22This+email+address+must+already+be+in+its+canonical+form.+Please+remove+aliases%2C+tags%2C+o...