Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Using WinSCP Windows app with Digital Ocean Spaces

Indeed, make sure you do not include the space/bucket name in the hostname. The hostname should be like fra1.digitaloceanspaces.com, not bucket.fra1.digitaloceanspaces.com. WinSCP adds the bucket subdomain on its own.
rogerpence

Re: Using WinScp Windows app with Digital Ocean Spaces

Update - fixed!

WinSCP doesn't want the endpoint that DO provides for the Space
DO gives you this:
https://my-assets.nyc3.digitaloceanspaces.com
Don't use that as the host. Use this
nyc3.digitaloceanspaces.com
as the WinSCP host name.

Your id and key lead WinSCP to the right DO bucket.

If you want to, put a folder (ie /images in the Remote Directory) – or just navigate there after WinSCP establishes the connection.
rogerpence

Using WinSCP Windows app with Digital Ocean Spaces

I'm trying to use the WinSCP Windows app to connect to Digital Spaces. I can get it to connect, but when uploading it says, "Specify target bucket."

I've every combination possible of using the DO Spaces name and folder name as the "remote directory" name – nothing works. I've tried:
/spacesname/foldername

spacesname/foldername
/foldername
foldername

I am able to successfully upload and download with CyberDuck – so I know the Spaces account is working correctly otherwise.

What am I missing? Thank you very much.