Error adding existing CloudFront

  • Resolved akamai32

    (@akamai32)


    7 months, 1 week ago

    Hello,

    I have an existing CloudFront distribution serving my WP, and I want to add it to W3TC so I can use auto-invalidation. I added the CloudFront domain and CNAME in the “Replace site’s hostname with” field, but then I click to test I get the error “Error: Distribution for origin “www.my-website.com” not found. The user permissions are correct (I’ve even tried attaching admin permissions and got the same error).

    The DNS https://www.my-website.com is pointing to the CloudFront distribution, so the origin domain is different (origin-www.my-website.com) since it points to an ALB, however I can’t edit or rename the field “Origin” on the W3TC configuration page.

    As part of the troubleshooting, I’ve tested adding a dummy origin with origin domain “origin-www.my-website.com” and the test passed.

    Is there a way to rename the “Origin” on the W3TC CDN Configuration? If not, what is the correct way to import an existing CloudFront distribution?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @akamai32

    Thank you for reaching out and I am happy to help!
    Can you pelase sahre which CDN type you are using (push or pull) in Performance>General settings, and can you please share the screenshot of the Performance>CDN settings so I can check this?

    Shareing the URL of the website would also be very helpful.
    Thanks!

    Thread Starter akamai32

    (@akamai32)

    Hi Marko,

    Thank you for your quick response.

    The CDN Type is Origin Pull -> Amazon CloudFront, and we don’t have a s3 bucket as origin, the only origin is the ALB I mentioned).

    Please find below a screenshot of the CDN configuration. For this test I’m using https://www.galassi.cloud as the website (so https://www.galassi.cloud resolves to the CloudFront distribution’s domain name, and a different domain resolves to my ALB’s domain name as the origin).

    • This reply was modified 7 months, 1 week ago by akamai32. Reason: Image didn't load directly
    • This reply was modified 7 months, 1 week ago by akamai32.
    • This reply was modified 7 months, 1 week ago by akamai32.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @akamai32

    Thank you for your feedback.
    Can you pelase share why you adeed https://www.galassi.cloud to as a CNAME?

    Also, can you please share what you are exactly trying to achieve, serving static files from the CDN or the Full site delivery?

    Thanks!

    Thread Starter akamai32

    (@akamai32)

    Hello Marko,

    I’ve added https://www.galassi.cloud to CNAME to reflect my current CloudFront distribution configuration which has it, but I tried with both the CloudFront domain name only and with the CNAME only and I got the same error message in both tests.

    I’m using the CDN for Full site delivery, https://www.galassi.cloud opens the WordPress website’s main page.

    Thank you!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @akamai32

    You cannot setup the FSD CDN this way. You enabled the CDN option for amazon, and the FSD CDN option is something else, and it’s just below the CDN Type in General settings.

    What you are trying to do canot be done with the CDN option

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error adding existing CloudFront’ is closed to new replies.