nostr:npub1hjw7g4r5apm9jsepkstufmcvgprlvfn674rug4n8nz4gtgjlr5pskjmghf have you checked your logs?

Here is my config for backblaze:

S3_ENABLED=true

S3_PROTOCOL=https

S3_REGION=eu-central-1

S3_ENDPOINT=https://s3.eu-central-003.backblazeb2.com

S3_HOSTNAME=s3.eu-central-003.backblazeb2.com

S3_READ_TIMEOUT=60

S3_BUCKET={your bucket name}

S3_ALIAS_HOST={your host name that you use to proxy your media data through your CDN}

AWS_ACCESS_KEY_ID={your keyID from B2}

AWS_SECRET_ACCESS_KEY={your applicationKey from B2}

More details at https://blog.thms.uk/2023/01/setting-up-mastodon#setting-up-backblaze-b2-for-mastodon

Reply to this note

Please Login to reply.

Discussion

nostr:npub1pq2m743ytcvz7n3ytksrw0ctprf3jtmtdnaewaz0qxsu6z4c2u6sw2d7dh

Thanks. I deleted my original post shortly after because I didn't use https:// for the s3_endpoint address.

Of note, it was one of your previous posts that made me reexamine those settings.

Thank you for replying and also, thanks for posting mastoadmin posts.