Backblaze S3 Configuration

[Alemiz112]

Hello, I have recently tried to set up Outline together with Backblaze S3 but I run into issues with CORS.
The Backblaze is denying the requests made against it because of No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I have configured CORS rules on Backblaze to allow any incoming requests as following:

"corsRules": [
        {
            "allowedHeaders": [
                "*"
            ],
            "allowedOperations": [
                "s3_head",
                "b2_download_file_by_id",
                "b2_upload_part",
                "b2_upload_file",
                "s3_put",
                "b2_download_file_by_name",
                "s3_delete",
                "s3_post",
                "s3_get"
            ],
            "allowedOrigins": [
                "*"
            ],
            "corsRuleName": "allowNotionUsers",
            "exposeHeaders": null,
            "maxAgeSeconds": 3600
        }
    ]

Than in Outline S3 settings are as following:

AWS_ACCESS_KEY_ID=<key-id>
AWS_SECRET_ACCESS_KEY=<access-key>
AWS_REGION=eu-central-003
AWS_S3_UPLOAD_BUCKET_URL=https://s3.eu-central-003.backblazeb2.com
AWS_S3_UPLOAD_BUCKET_NAME=<bucket-name>
AWS_S3_UPLOAD_MAX_SIZE=26214400
AWS_S3_FORCE_PATH_STYLE=true
AWS_S3_ACL=public-read

Is there something what I forgot to adjust in order to make it work?

[tommoor]

I don't have an example of a working setup in Backblaze, but if the CORS error is coming from the request to the backblaze server then it will be a configuration error there rather than in Outline itself. I'd recommending opening CORS all the way up first, and then gradually add rules to lock it down as an effective way of debugging.

Please post a working config once you figure it out!

[Alemiz112]

After few days I got this reply from the BackBlaze: Please note that Authorizations must be done on a system, and not on a browser, and access-control-allow-origin is not supported with authorization.

[kerberjg]

I can confirm we have the same problem, the only difference is that we use an ACL value of 'private'.
Does B2 even support 'public-read'? Doesn't seem to be an option

[kerberjg]

I have also contacted Backblaze support, they gave me a different reply. So far it seems they're not implementing CORS on their side correctly

[kerberjg]

After a few days of exchanging emails, here's the answer I got from Backblaze's staff:

I do apologize, while uploading via POST is part of the S3 API, it is not supported in our S3 Compatible API.
As per the previous link, all upload operations require a PUT command.

• Upload Part (PUT)
• Upload Part Copy (PUT)

I can certainly bring this up with our team to see if this functionality can be implemented in the next iteration of the API.

The only solution there would be to use Minio Gateway as a proxy in front of B2 to provide this functionality, or switch to a different S3 provider for the time being.

While Outline could implement backend S3 uploads, I don't think it's a good idea.

[kerberjg]

That's nice, thank you! I'll let you know if anything changes Backblaze-wise

[ToshY]

The only solution there would be to use Minio Gateway as a proxy in front of B2 to provide this functionality, or switch to a different S3 provider for the time being.

Minio Gateway functionally is actually deprecated.

@kerberjg Is the conclusion for now that Backblaze cannot be used directly?

[kerberjg]

Ah, I didn't know! Thanks for telling me. We've been running it in production for a few years now.

About Backblaze, you're correct

[lrstanley]

Ran into the Backblaze issues as well. I looked into Minio Gateway, however it being deprecated... I decided to just use AWS for the s3 bucket, making sure to carefully tune to where I'm not paying a pretty penny for using it. 😅

[looeee]

I looked into Minio Gateway, however it being deprecated...

This is frustrating, but you can always just not upgrade minio.

[looeee]

I started a compatibility table at the bottom of the documentation, here:

@tommoor that's awesome! Any idea if Cloudflare R2 works?

[danjenkins]

@looeee cloudflare r2 doesn't work, i get given a 400 bad request from r2 :(

[spacec0de]

r2 works for me, did you try deleting the bucket name from the end of the URL and using region us-east-1?

[danjenkins]

interesting, it didnt like doing cors etc even when it was enabled when I tried... can you better document your setup around r2 entirely? I can then double check it?

[Niek]

@spacec0de would you mind sharing your AWS_* env vars and your Outline version? I can't get it working with 0.68.1 + R2, see also: #4480 (comment)

[AndrewBucklin]

@spacec0de - Would also be interested in seeing what you use for these environment variables for getting Cloudflare R2 storage working:

AWS_REGION
AWS_S3_ACL
AWS_S3_FORCE_PATH_STYLE
AWS_S3_UPLOAD_BUCKET_NAME
AWS_S3_UPLOAD_BUCKET_URL
AWS_S3_UPLOAD_MAX_SIZE

Of course, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are self-explanatory.

[ToshY]

Has there been any updates on this? Still would very much like to be able to use Backblaze with Outline.

[tommoor]

You would have to contact Backblaze support to see if they’ve enabled that functionality

[mjeammet]

Very similarly, I've been trying to use Outline with French cloud provider OVH and could not make it work. It seems that uploading via POST is not supported by the API.

Scaleway, on the other hand, seems fully compatible.

I'm unsure how to edit the list of S3-compatible services but I think these compatibilities should be listed.