Rn21200 + ReadyNAS 6.10.6 will not accept my Baclblaze B2 S3 bucket
I have created an S3 bucket in the Backblaze B2 cloud storage system. When I try to enter the data (per https://kb.netgear.com/000038419/ReadyNAS-OS-6-Sync-with-Amazon-S3) using the ReadyNas S3 interface and current firmware, it won't display the bucket and there's no place, contrary to the article, to create a new one on the fly. My key appears to have the necessary permissions. Any idea why the bucket name isn't appearing? See the two screenshots.
Model: RN21200|ReadyNAS 212 Series 2- Bay (Diskless)
Re: Rn21200 + ReadyNAS 6.10.6 will not accept my Baclblaze B2 S3 bucket
FYI: friendly suggestion is to black out your Amazon S3 keys in your screenshots...this one you posted includes pretty much everything needed to log into your Amazon S3 bucket!
That said, you need to set the S3 Server URL to 'Customized URL' and use the URL from your B2 Cloud Storage bucket info, e.g., https://s3.us-west-002.backblazeb2.com.
That said, I am experiencing the problem where it was working for months and then stopped...just a guess that it may be related to the recent log4j hack/issue affecting Amazon S3 services but I'm not 100% sure. All I know is that I can log into my Backblaze B2 Amazon S3 account using my Backblaze keys via FileZilla using the Backblaze API address but I cannot use those same credentials in the ReadyNas 6.10.6 Amazon S3 setup screens any more. Am getting the same 'Failed to list Amazon S3 buckets. Failed to list buckets. Code 37007000029' error when using the proper Cutomizied URL for my Backblaze Amazon S3 hosted storage bucket.
Re: Rn21200 + ReadyNAS 6.10.6 will not accept my Baclblaze B2 S3 bucket
Thanks. I was missing the Customized URL part but as you said the problem persists. This seems like a serious issue without any sort of workaround. It would be nice to hear an acknowledgment of it from Netgear support. I'm querying Backblaze and will report any response. It's a classic multivendor problem, "Must be the other guy's fault."
Thanks also for the friendly suggestion: any key info I display is from no longer existent keys.
