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
- Download appwrite Docs
Is there is a way to download appwrite Docs ? Because appwrite skill isn't enough to give the agent full understanding about how appwrite works (I noticed this ...
- Appwrite Cloud Project shutdown due to i...
My appwrite projects gets shut down saying due to inactivity, but our platform gets users everyday with many requests to database and storage. so why all of a s...
- fastly error
Hey! I'm hitting a Fastly error on the www version of our site, but the root domain works fine. We have a wildcard set up, so I expected the subdomain to be cov...