With applications such as CyberDuck, MountainDuck, or Wasabi Explorer, you may encounter an issue displaying the contents of buckets that are using an all-numbered naming schema (such as 123456789). For example, Wasabi Explorer will generate a "Failed to parse location-constraint" error:
If your bucket name follows this schema and you are having issues viewing the bucket contents, try one of the following options to remedy the issue. If you continue having issues with your bucket after trying the options below, contact Wasabi Support.
Option 1: Rename the Bucket to Include Additional Characters
Renaming the bucket to include additional characters, such as a letter or a dash, can help remedy the issue.
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. For example:
Click RENAME BUCKET, and you should see a Success message at the top of the page:
Test your bucket with the application again to see if the error is resolved.
Option 2: Migrate to a New Bucket
If renaming your bucket does not work as expected, migrate your bucket data to another bucket with a more preferred naming schema (for example, mybucket12345 rather than 12345). If you have a small amount of data in your bucket and prefer to move it manually, applications such as S3 Browser and AWS CLI do 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 significant amount of data in your bucket and prefer to use an automated migration method, review Migrating Data From One Wasabi Bucket to Another Wasabi Bucket