Skip to content
Back

Sudden CORS Errors - Domain hasn't Changed, Used to Work Previously with `*` Wildcard

  • 0
  • Web
  • Cloud
Dan6erbond
11 Mar, 2026, 17:12

I have an Appwrite project with two web apps configured, the first one has the hostname * and the second one I just added to test if it could fix the issue with the specific hostname of my Appwrite-hosted site. Previously * worked fine, now even with the specific hostname I'm getting these errors:

TypeScript
Access to fetch at 'https://fra.cloud.appwrite.io/v1/teams/69b1560c0009057775d8/memberships?queries%5B0%5D=%7B%22method%22%3A%22equal%22%2C%22attribute%22%3A%22userId%22%2C%22values%22%3A%5B%2269627c1e0022144128ce%22%5D%7D' from origin 'https://skincare-buddy.appwrite.network' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Not sure what exactly I can do to fix this.

TL;DR
Sudden CORS errors after a refactor, even with specific hostname. User resolved the issue by properly setting the AppWrite Project ID in the client.
Dan6erbond
11 Mar, 2026, 17:21

Nevermind. I'm dumb. Did a big refactor and the client didn't have the AppWrite Project ID properly set. How can I close this?

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more