We have noticed an issue with some applications, such as CyberDuck, MountainDuck, and Wasabi Explorer, having issues displaying the contents of buckets that are using an all-numbered naming schema (for example 123456789). For example, Wasabi Explorer will generate an Failed to parse location-constraint. error:
If you find that you are having similar issues with viewing the contents of your bucket, and your bucket name follows this schema, then please try one of the following steps to remedy the issue:
Option 1: Rename the bucket to include an additional character type
We have found through testing that renaming the bucket to include additional characters, such as a letter or a dash, can help remedy the issue. Please see the following screenshots for details on how to rename your bucket:
In the Wasabi Console, click the menu button to the right of the bucket.
Click Rename.
Rename your bucket to include additional character types, preferably letters.
Click Rename Bucket, and you should see the Success pop-up at the top of the page.
Test your bucket with one of these applications again to see if you encounter the same error.
Option 2: Migrate to a new bucket
If renaming your bucket does not work as expected, we recommend migrating your bucket’s data to another bucket with a preferred naming schema (for example, mybucket123). If you have a small amount of data in your bucket and would prefer to move it manually, applications such as S3 Browser and AWS CLI have been found to not have any issues with the numbers-only naming schema, and you may use these applications to move your data between buckets.
If you have a lot of data in your bucket and prefer to use an automated method of migration, then please check out our KB article How can I migrate my data from one Wasabi bucket to another Wasabi bucket?
If you continue to have issues with your bucket after trying the above methods, please reach out to us at support@wasabi.com.