When running a profile targeting a Wasabi storage bucket you may receive the error "Failed to scan files: Cloud error 200: HTTP/1.1 200 OK".  A reason for this error could be that your bucket name consists only of numeric characters (e.g. 1234). Other applications may work fine with such a bucket because they are accessing it using path-style REST methods (e.g. GET s3.wasabisys.com/bucket-name/object) where on the other hand SyncBackPro accesses the bucket using its virtual host name (e.g. GET bucket-name.s3.wasabisys.com/object), which is the preferred method as per Amazon S3 documentation.

The only way to resolve this error, when using a Wasabi bucket with SyncBackPro, is to ensure that the bucket name starts with a letter. Based on this article the bucket name should begin with a lowercase letter. For some unknown reason, the Wasabi web UI allows users to create buckets that don't follow their own rules.