Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Daniel Colquitt (daniel@colquitt.xyz)'s status on Friday, 21-Feb-2025 18:26:21 JST Daniel Colquitt

   in reply to

   @cadusilva I've figured it out. Previously I was routing my images through the S3 front end, e.g., `s3.eu-central-000.backblazeb2.com`, but it looks like Backblaze made a change to the hostname so that it is `<BUCKET NAME>s3.eu-central-000.backblazeb2.com`. I've changed my CDN to use the friendly hostname `f000.backblazeb2.com` and everything seems to work fine now.

2. Embed this notice
   Cadu Silva :verified: (cadusilva@bolha.one)'s status on Friday, 21-Feb-2025 18:26:20 JST Cadu Silva :verified:

   in reply to

   @daniel here the setup is as follows:

   The media is uploaded to <s3.eu-central-000.backblazeb2.com> as endpoint, but the instance bucket is private.

   I'm using Bunny CDN, which authenticates with B2, downloads the media from <BUCKET-NAME.s3.eu-central-000.backblazeb2.com> and then shows it to the user.

   So I guess that's why I didn't see this error so far. I'm already using the URL with the bucket name.

   But anyway, good thing that you found the problem and fixed it in just one hour.

   Cheers!