Finally started working on getting my PerKeep server up and running and ran into a snag while trying to use B2 Clound Storage.
It looks to be an issue with changes they made to the v1 API on July 26, 2018 https://www.backblaze.com/b2/docs/versions.html. It says in short: This release was incompatible with previous releases because it broke an (unwritten) rule that once you authenticate, all of the calls will be authorized. If you authenticate with an application key that has restricted capabilities, is restricted to a bucket, or is restricted to a file name prefix, some calls will return a 401 Unauthorized. I am running into several issues while using a key restricted to a single bucket. 1. If I try to use the accountid and the application key perkeep exits with: b2 remote error [unauthorized] I also tested this with an unrestricted key with the same result. Also confirmed with curl https://api.backblazeb2.com/b2api/v1/b2_authorize_account -u "accountid:applicationkey" 2. I can authenticate if I use the KeyID as the accountid and the application key but then perkeep exits with: Post https://api002.backblazeb2.com/b2api/v1/b2_list_buckets: b2 remote error [bad_request]: accountId invalid. If anyone is using B2 and can confirm or deny that it is working that would be great as I seem to be dead in the water until I get a chance to look under the hood. Any assistance would be great. Thanks, Clayten -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
