You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am also seeing this issue since upgrading to 8.0.0. I can connect to the S3 bucket and see the top level prefixes, but if I try to drill down I get the above error. I have tried the same bucket configuration with 7.10.0, 7.10.1 and 7.10.2 and they all work.
The credentials I am using are for a user with limited access to my S3 account. This user only has permissions on this bucket, not ListAllBuckets.
I am also seeing this issue since upgrading to 8.0.0. I can connect to the S3 bucket and see the top level prefixes, but if I try to drill down I get the above error. I have tried the same bucket configuration with 7.10.0, 7.10.1 and 7.10.2 and they all work.
The credentials I am using are for a user with limited access to my S3 account. This user only has permissions on this bucket, not ListAllBuckets.
Make sure you either set the bucket name in the default path or with the virtual hostname notation as in bucketname.s3.amazonaws.com.
The specified bucket does not exist. Please see attached printscreen.
Attachments
Cyberduck_error.JPG
(48.8 KiB)The text was updated successfully, but these errors were encountered: