Question

DO Spaces returns 403 error when Wordpress edits files.

Posted September 20, 2021 86 views
WordPressDigitalOcean Spaces

So I have a WordPress Droplet that is using DO Spaces for its files. When ever a file is changed(regenerate thumbnails, rotate and image) DO Spaces then responds with a 403 Error for that file. Is this a configuration issue? How can I solve this.
I am using the DO Spaces plugin.

1 comment
  • This is what the error looks like:

    <Error>
    <Code>AccessDenied</Code>
    <BucketName>cc-backs</BucketName>
    <RequestId>tx00000000000009826ac32-006148cb70-185f37a7-nyc3b</RequestId>
    <HostId>185f37a7-nyc3b-nyc-zg02</HostId>
    </Error>
    

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

Hey @fredblueshoon

I suspect that this error is due to the permissions on the object. By default, all the objects in your bucket have Private permission. You will need to access them after authorizing them with the secret-access key pair.

If you want to access it directly without creating signed URLs, you can change the permission to Public.
Read more about changing the permissions using Cloud Dashboard https://docs.digitalocean.com/products/spaces/how-to/set-file-permissions/#change-file-permissions

I hope this helps :)

  • This isn’t quite it. Here is the URL to that file
    https://cc-backs.nyc3.digitaloceanspaces.com/cms-plein-air/2020/12/Sophie-Avocado-e1632090092342.jpg
    This file doesn’t show up on my Spaces where this path points to. It seems like when WordPress tries to write a file it writes the file, but then can’t read it? When I get a chance I’ll have to look on S3 to see if it exists there.

    • I think it is better to check by uploading manually to the bucket from either cloud panel or Filezilla etc and see if the objects stay there. If there are no problems uploading via other means, it must be some issue with the tool.
      Again, a private object will not be accessed without proper authorization.