Cloudflare

i believe your bucketname needs to be called: cdn-bucket-name

so recreate a bucket called: cdn-bucket-name

then create your cname: cdn-bucket-name to point to your s3 path

and then your path cdn-bucket-name.yourdomain.com can work.

The fix is not related to this plugin.

• This reply was modified 5 years, 3 months ago by jiggaman.

Thanks for this.

If I change the CNAME record from “cdn” to “cdn-bucket-name” – then if I got to cdn.domain.com it will go nowhere.

It is not directly related to the plugin but there is a tutorial for this and there is a setting to set a custom domain so it kind of is related.

Are you saying to change the cname to be:

name: cdn-bucket-name
Content: cdn-buket-name.s3-eu-west-2.amazonaws.com

Not sure how this will work?

Thanks for the comment to help me

Figured it out.

You need to have the bucket name as:

cdn.domain.com

and your cname record as:

name: cdn
content: cdn.buket-name.s3-eu-west-2.amazonaws.com

This works for me now

https://deliciousbrains.com/wp-offload-media/doc/cloudflare-setup/

Actually…i think the correct url is cdn-bucket-name.domain.com then you create your cname cdn-bucket-name to point to cdn-bucket-name.s3-eu-west-2.amazonaws.com

Right?

No @jiggaman, the bucket name must match the custom domain name you want to use, as per the “IMPORTANT” note at the top of the documentation that I linked to.

This is a quirk of how Cloudflare accesses the bucket, most other CDNs can use normal bucket names.

So, if your apex domain in Cloudflare DNS is “example.com”, and you want to use “cdn.example.com” as your custom CDN domain name, then you would create an S3 bucket called “cdn.example.com”.

If that bucket was in the “eu-west-2” region, then you would add a CNAME entry to Cloudflare DNS with a name of “cdn” and a target of “cdn.example.com.s3-eu-west-2.amazonaws.com”.

@ianmjones yes…argg…my bad.