Wasabi + Cloudflare Issues

Hi I have an issue configuring Wasabi with Cloudflare. I have created a CNAME sub (sub.domain.cyou) and the content is s3.eu-central-1.wasabisys.com. But it gives me error like this:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

NoSuchBucket
The specified bucket does not exist
sub.domain.cyou
D8465B7BBF4C534B
y7nhir/YbN/e8tGsAD/xUvTxSwlH/h813zaSD2S/wmxkVqetzCkMvb09YIZeCombNrvIaLosN4w+

I also have tried to bypass the Cloudflare Proxy. I have contacted Wasabi but they said I need to check my Cloudflare setting because the Wasabi-end is working fine.

And here is my policy:

{
“Version”: “2012-10-17”,
“Statement”: [
{
“Sid”: “AllowPublicRead”,
“Effect”: “Allow”,
“Principal”: {
“AWS”: “ "
},
“Action”: “s3:GetObject”,
“Resource”: "arn:aws:s3:::bucketname/
”,
“Condition”: {
“IpAddress”: {
“aws:SourceIp”: [
“173.245.48.0/20”,
“103.21.244.0/22”,
“103.22.200.0/22”,
“103.31.4.0/22”,
“141.101.64.0/18”,
“108.162.192.0/18”,
“190.93.240.0/20”,
“188.114.96.0/20”,
“197.234.240.0/22”,
“198.41.128.0/17”,
“162.158.0.0/15”,
“172.64.0.0/13”,
“131.0.72.0/22”,
“104.16.0.0/13”,
“104.24.0.0/14”
]
}
}
}
]
}

I have checked the similar threads but nothing fix the issue. Please anyone help me. Thank you.

If you mean you paused Cloudflare, then we can most certainly rule out Cloudflare as it only provides DNS in that case.

I’d suggest to leave it paused and to contact your service provider once again, so they clarify what the exact issue is. If you have the right domain associated and the right hostname in your CNAME it should work and if it doesn’t it’s something they need to fix.

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