cyberduck s3 we encountered an internal error

So I had to drill into every single folder and subfolder and change the permission for every single file. You cannot set the permission on folder level (e.g. So the only option I found was to use the web interface after uploading the files to then manually select the uploaded files to change the permission to public. So it seems that Spaces sets the default permission for every uploaded file not uploaded via the web interface to private. So the good vibes of the successful started started to fade quickly.Īll files uploaded via Cyberduck resulted in a AccessDenied error message: But the ones uploaded via Cyberduck were not.

The files that were uploaded with the web interface were available via CDN endpoints right away. After creating an access key for Spaces (Digital Ocean Dashboard > API > Spaces access keys) I was able to login via Cyberduck successfully. So I was happy to see that Digital Ocean officially supports and recommends the free FTP/tranfser application Cyberduck. The web interface is ok, but not really usable for lots of file transfers and folder structuring. Just took me less than a minute to activate that product and create my first space and upload some test files via the Digital Ocean web interface. The other day I was looking for a simple and affordable CDN solution so I checked their Spaces product. I am a big fan of Digital Ocean because they simplify the entire cloud platform world and make it accessible for people who don’t set up and administrate cloud servers daily. Digital Ocean Spaces and Cyberduck are a great match… if you know how to set it up properly… Background and Problem

Cyberduck s3 we encountered an internal error