Question

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

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.

Show comments
Submit an answer


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!

Sign In or Sign Up to Answer

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.

xarielx • June 3, 2023

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

Bobby Iliev
Site Moderator
Site Moderator badge
• 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"

  1. Go to your DigitalOcean Spaces dashboard.
  2. Click on the desired Spaces bucket.
  3. Navigate to the “Settings” tab.
  4. Find the “CORS Configuration” section and click on “Edit CORS Config”.
  5. Make sure you have the following settings:
  • Allowed Origins: https://*.ondigitalocean.app
  • Allowed Methods: GET, HEAD
  • Allowed Headers: Content-Type, Origin, Accept
  1. 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

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.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up