403 Forbidden Access Denied when trying to access my space

Posted April 23, 2020 4.2k views
DigitalOcean Spaces

I created a new space, enabled CDN, created a subdomain and an SSL for it.

I also made sure that all my files are set to Public.

But when I try to access the files in my space in my code I get this error:

Error executing “ListObjects” on “{URL}”;
AWS HTTP error: Client error: GET {URL} resulted in a 403 Forbidden response:
<?xml version=“1.0” encoding=“UTF-8”?>
<BucketName>{space name}</BucketName>
<RequestId> (truncated…) AccessDenied (client): -
<?xml version=“1.0” encoding=“UTF-8”?>
<BucketName>{space name}</BucketName><RequestId>tx00000000000002d263f75-005ea1b9f0-1fd80b0-fra1a</RequestId>

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.

Submit an Answer
1 answer


Do you try to add the CORS Configurations?

Dashboard –> Space –> Select your Spacename –> Settings –> CORS Configurations –> Add and you can add your website and select just GET.

Let me know.

  • Hi.

    I have a very similar problem: I have installed a docker registry on managed kubernetes following this tutorial, but I am also getting this error. The CORS definition needs a domain name, but I am trying to access the docker registry from my workstation which does not have a domain assigned to it. Do I need one or is there another way ?

    Thank you.

    by Savic
    A private Docker registry allows you to securely share your images within your team or organization. By hosting your private Docker registry directly in your Kubernetes cluster, you achieve higher speeds, lower latency, and better availability, all while having control over the registry. In this tutorial, you'll deploy your private Docker registry to your DigitalOcean Kubernetes cluster using Helm, backed up by DigitalOcean Spaces.