Related

Product DigitalOcean Spaces: Simple Object Storage Product
How many subdomain can I have per droplet ? Especially if I buy 5$ droplet space? Question Question
Why does my droplet power off on its own yet it has been working well ever since? Question Question

Question

Access denied for new file uploaded to Spaces when accessing via custom Subdomain and Edge URL

Posted March 3, 2020 1.7k views
DigitalOcean Spaces

Hey,

I have the issue that when accessing newly uploaded files via the custom subdomain or edge url for my spaces CDN, I get a access denied error. The file is fine when accessed via the Origin URL, but the edge and custom domain urls give me a XML response which says access denied. The permission is correctly set.

After issuing a purge request for that file it works.

How can I fix this?

Add a comment
ffritz
By:
ffritz
Add a comment
2 comments
  • s4suryapal August 28, 2020
    Reply Report

    I am getting same in case of GIF and JPG. Please share details if you solved it.

    In my case only SUBDOMAIN not working. Origin and Edge both working.

    When trying to access file via subdomain getting permission error, even i set permission as public-read.

    I tested other file format. VIDEO and MP3 working well. Only issue with JPG and GIF

    Please share if you have any solution

  • ebrahym September 6, 2020
    Reply Report

    same issue with jpeg images - works at origin but gives error when edge url is accessed… Anyone here can help???

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.

×
7 answers
zicodeng April 24, 2020

How is this not getting much attention? This seems to be a big issue that basically makes DO Space useless

Reply Report
  • zicodeng June 13, 2020

    It seems the issue is mostly caused by gif image???

    Reply Report
    • swayer July 16, 2020

      I’m getting the same with CSS and purging isn’t doing the trick. Origin is fine, edge and subdomain throw net::ERR_ABORTED 403 (Forbidden)

      I have three CSS files in the same directory, but only one is working across all three URLs.

      EDIT: Renaming the file after upload got it working. Renaming it back to the original throws 403 again.

      UPDATE: When I first created the CSS directory, I misspelled it. I renamed it and uploaded three CSS files into it. Only one worked on upload.

      I deleted the CSS directory I had just created (and renamed) and created a new CSS directory. I re-uploaded the CSS files public and fresh. Worked.

      Reply Report
    • rob3447 July 22, 2020

      PNG images also.

      Reply Report
EricMathison March 30, 2020

Having the same issue. It only happens on 50% of the files I upload.

Reply Report
jasper June 24, 2020

I also get a 403 access denied

user@app-w-1:~/domain.com/current/storage/logs$ tail -n 70 laravel.log
[previous exception] [object] (GuzzleHttp\\Exception\\ClientException(code: 403): Client error: `PUT https://app-stuff.ams3.cdn.digitaloceanspaces.com/assets/logo.domain.com/js/site.js` resulted in a `403 Forbidden` response:
<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error><Code>SignatureDoesNotMatch</Code><RequestId>tx0000000000000198831c1-005ef2 (truncated...)
 at /home/forge/domain.com/releases/145/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113)
[stacktrace]

Origin does work. Looking into way to put using origin and load using EDGE.

Reply Report
baskettcase October 8, 2020

Im also having this issue which indeed is making CDN unusable. I have to point everything to Origin since that seems to work fine.

Reply Report
davidtgill November 2, 2020

Yes me too.
Crazy that there is no response. This is a big problem?
This has been an issue for 2 years now.

Reply Report
davidtgill November 3, 2020

The only fix I have found is to:

Manage Permissions -> Public

Before you click on the CDN link.

Reply Report
Malcs November 26, 2020

I was getting the exact same issue.

I found out my issue was due to Cloudflare caching. I purged the cache for the subdomain and also switched to DNS only for the CNAME in the control panel. This fixed it straight away.

Hope this helps.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help