Post a reply :: Support Forum

martin

2021-08-31

@Guest: Please attach a full session log file showing the problem (using the latest version of WinSCP). And also a log file from S3 browser.

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Guest

2021-08-30 08:17

I'm still having this issue even if configuring the region from the dropdown menu:

The eu-south-1 location constraint is incompatible for the region specific endpoint this request was sent to.

With the same set of key/secret S3 Browser is working fine.

martin

Re: AWS S3 Bucket in Cape Town region not accessible

2020-04-30

Anyway, the new version will allow your to select them:
https://winscp.net/tracker/1864

martin

Re: AWS S3 Bucket in Cape Town region not accessible

2020-04-30

But you can type it.

pcza

Re: AWS S3 Bucket in Cape Town region not accessible

2020-04-30 08:18

It is not possible to select the af-south-1 region from within the current version of WinSCP.

There is also no provision to select the new Milan Italy region eu-south-1 in the current version of WinSCP.

martin

Re: AWS S3 Bucket in Cape Town region not accessible

2020-04-30

I do not see what WinSCP should be doing differently.
Wouldn't it help to change the default region?
https://winscp.net/eng/docs/ui_login_s3

pcza

Re: AWS S3 Bucket in Cape Town region not accessible

2020-04-30 07:38

Log file attached

martin

Re: AWS S3 Bucket in Cape Town region not accessible

2020-04-30

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.