Offloaded media URLs may be broken (Received 404 from endpoint)

  • Resolved gif1

    (@gif1)


    1 year, 7 months ago

    Hey Guys,

    First-time user of the plugin. Set to use a storage bucket on S3 and Cloudflare as a CDN. I’m using a custom domain name, which appears to work. If I upload files and check the storage bucket, assets are available, and the URL details (in the media library) show the right custom domain URLs. What they don’t show is a preview of the image.

    In the Delivery Settings of the plugin, I get the following error –

    “Offloaded media URLs may be broken. An error was encountered while testing the domain: Received 404 from endpoint“

    Any ideas where I’m going wrong with this?

    TIA

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Delicious Brains

    (@deliciousbrains)

    Hey @gif1,

    There’s a couple of things that users of Cloudflare often trip up on.

    The bucket name must be the same as the domain that it’s media is going to be served from. E.g. for site “example.com” where the media is to be served from the domain “cdn.example.com”, the bucket must be named “cdn.example.com”.

    The second thing people trip up on is setting up Cloudflare’s DNS entry for the CNAME, it must include the bucket’s region in the amazonaws.com domain, unless the bucket’s region is us-east-1.

    So for the London bucket region, eu-west-2, the CNAME target might be:

    cdn.example.com.s3.eu-west-2.amazonaws.com

    But if you’re using the default us-east-1 region for the bucket, then it should not include the region:

    cdn.example.com.s3.amazonaws.com

    The above, and some details on setting up HTTPS etc are in our Cloudflare Setup for Amazon S3 doc: https://deliciousbrains.com/wp-offload-media/doc/cloudflare-setup/

    If that doesn’t help, please post your site’s Diagnostic Info from the Help tab in WP Offload Media, and I’ll take a look to see if I can spot a problem.

    -IJ

    Thread Starter gif1

    (@gif1)

    Hey Guys,

    A big thanks for the quick follow up. It took a bit of time to get my head around the naming issue, mostly because at the point of naming, I don’t appear to be able to use “.” (full-stops) in the name. So, my domain name (which is a .com) one isn’t allowed. The article from AWS (https://is.gd/8PSX1H) says the same, I can’t use full-stops in the name. I’m not sure how others are getting around this?

    Cheers,

    Plugin Support Delicious Brains Support

    (@dbisupport)

    Hi @gif1 ,

    Thanks for the response!

    If Amazon Lightsail is needed to create the bucket then unfortunately, Cloudflare won’t work and you’ll have to opt for another CDN such as CloudFront instead.

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

    Another option is to just use a proper S3 bucket since that allows “.” on the bucket name which most of our customer uses.

    https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html

    https://deliciousbrains.com/wp-offload-media/doc/amazon-s3-quick-start-guide/

    Please let us know if you have any further questions.

    Thread Starter gif1

    (@gif1)

    Hey,

    Thanks for the quick follow up.

    I wasn’t aware of bucket and bucket proper, etc. but following up on your point landed me in the primary AWS services menus and S3 directly, which has no problem with full-stops ?? All good.

    Hopefully that should do it when I get to that point.

    Cheers,

    Thread Starter gif1

    (@gif1)

    Issue solved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Offloaded media URLs may be broken (Received 404 from endpoint)’ is closed to new replies.