Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

How to fix: has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Posted on April 12, 2023

DigitalOcean Spaces

HTML

Object Storage

DigitalOcean App Platform

Django

By Thomas Doll-Datema

Hi,

I am hosting a few fonts for my Django application on spaces. They were working ok for a little bit but now I get this error:

has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

How do I fix this? I have set the CORS policy on Spaces for this bucket as follows:

Origin: https://*.ondigitalocean.app

Allowed Method: GET HEAD

I do not know what to do with allowed headers. Any help would be much appreciated.

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Thomas Doll-Datema

April 14, 2023

I do not currently have a domain attatched to the app as it’s still in development. As soon as its finished I’ll set it to one. for now I’m using randomlink.ondigitalocean.app which is why I set it to *.ondigitalocean.app.

Bobby

April 14, 2023

Hi there,

It seems like you have the correct CORS policy for the origin and allowed methods, but you might be missing the required headers.

What I could suggest is to try and add the appropriate Access-Control-Allow-Headers for your DigitalOcean Spaces bucket"

Go to your DigitalOcean Spaces dashboard.
Click on the desired Spaces bucket.
Navigate to the “Settings” tab.
Find the “CORS Configuration” section and click on “Edit CORS Config”.
Make sure you have the following settings:

Allowed Origins: https://*.ondigitalocean.app
Allowed Methods: GET, HEAD
Allowed Headers: Content-Type, Origin, Accept

Save the changes.

Let me know how it goes!

For more information about this you can check out the documentation here:

https://docs.digitalocean.com/products/spaces/how-to/configure-cors/

Best,

Bobby

xarielx

June 3, 2023

OMG I HAVE THE SAME ISSUE NOW, its driving me crazy. I have tried everything

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Thomas Doll-Datema

April 14, 2023