
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeI can see what's happening here! The issue is that Sanity's CORS Origins configuration doesn't support wildcard patterns for subdomains like https://*.HOSTNAME.se. You need to add each specific subdomain individually.
Based on the CORS Origins documentation, here's what you need to know:
Why wildcards don't work: Sanity requires you to explicitly whitelist each complete domain with its full protocol. This is a security best practice to prevent unauthorized access to your content.
What you need to do:
For your address https://canary.www.HOSTNAME.se, you need to add the exact, complete URL to your CORS origins:
https://canary.www.HOSTNAME.seFor multiple domains:
If you have several subdomains (like canary.www.HOSTNAME.se, staging.www.HOSTNAME.se, production.www.HOSTNAME.se), you'll need to add each one individually as a separate CORS origin entry. It's a bit more manual work, but it provides better security control over which domains can access your Sanity project.
Important note: The protocol matters! http:// and https:// are treated as different origins, so make sure you're adding the exact protocol you're using.
If you're still getting CORS errors after adding the exact domain, double-check that:
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
Content operations
Content backend


The only platform powering content operations
By Industry


Tecovas strengthens their customer connections
Build and Share

Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag store