Issue with Wasabi bucket

Hi there,

We would like use Cloudflare in front of a wasabi bucket, so that we use caching and CDN, and also our own subdomain.
We have a setup a CNAME record for the wasabi bucket.

In this example, the file bellow is public and can be accessed directly from your service:

https://s3.eu-central-2.wasabisys.com/xen-prod/******.jpg

The CNAME translates our subdomain xendata.********.com to s3.eu-central-2.wasabisys.com and is reversed-proxied on Cloudflare.

But when trying to access the same file, we get an error from your service:

https://xendata.***.com/xen-prod/.jpg

<Error>

<Code>NoSuchBucket</Code>

<Message>The specified bucket does not exist</Message>

<BucketName>http://xendata.********.com/</BucketName>

<RequestId>D0737B39F5DDC38E</RequestId>

<HostId>yGareeP44GwuVY0ym7PzFMVgP2SJbSZgGopeTOVrjDacND02QX5OfE5GtD9IE3fdFiAXKATdI3lI</HostId>

</Error>

As it seems, wasabi looks for the HOST header to serve a bucket?

Is there a workaround to this?

Thanks

Alex

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.