gdevelek

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [W3 Total Cache] Problem enabling AWS Cloudfront
    Thread Starter gdevelek

    (@gdevelek)

    1 year, 1 month ago

    Hello @vmarko ,

    I don’t know what you mean by “FSD CDN” and “asset deliver CDN”. As mentioned I’m trying to enable AWS Cloudfront. The URL is wp-test.fieldcode.com. The Cloudfront URL is dklb1gj24syd2.cloudfront.net

    Forum: Plugins
    In reply to: [W3 Total Cache] Problem enabling AWS Cloudfront
    Thread Starter gdevelek

    (@gdevelek)

    1 year, 1 month ago

    Marko, thanks for responding!

    I’m not sure why you posted the 1st video, I’m not using S3. Am I missing something?

    I followed the 2nd one, but no success. The “curl” test fails at the end, and nothing has been fixed on the browser. I use a URI that is promptly returned when I use the “proper” (non-cloudfront) DNS name in front, let’s call it wp.mycompany.com. But with the CF domain it fails with 502 as shown below.

    I tried both with “legacy cache” and with “cache policy and origin request policy”, per the video.

    I have added my proper DNS as an “alternate domain name” on the AWS, is that correct? And I have not added a CNAME in the W3TC page.

    GET /wp-content/themes/twentytwentyfour/assets/fonts/cardo/cardo_normal_400.woff2 HTTP/2
    Host: dk4l1gj24syd2.cloudfront.net
    user-agent: curl/7.68.0
    accept: /
    origin:wp.mycompany.com

    • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    • Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
      < HTTP/2 502
    • < content-type: text/html
    • < content-length: 507
    • < server: CloudFront
    • < date: Tue, 06 May 2025 15:26:58 GMT
    • < expires: Tue, 06 May 2025 15:26:58 GMT
    • < x-cache: Error from cloudfront
    • < via: 1.1 2e14fb9d8f93852aec2f703fe567e56c.cloudfront.net (CloudFront)
    • < x-amz-cf-pop: ATH50-C1
    • < alt-svc: h3=”:443″; ma=86400
    • < x-amz-cf-id: J5S20DqQUsq26c4H4s7AM0sGigHRto2GbYAWM2UwaemzyPp29GspJw== <
      ERROR: The request could not be satisfied
    • ERROR Failed to contact the origin.

Viewing 2 replies - 1 through 2 (of 2 total)