502 Cloudfront Errors

  • Resolved seoservicesla

    (@seoservicesla)


    4 years, 7 months ago

    W3 Cache Plugin is timing out on a daily basis. We are seeing this error consistently:

    502 ERROR
    The request could not be satisfied.
    The origin closed the connection. We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
    Generated by cloudfront (CloudFront) Request ID: NlBkOp1Uij047s0MFrE7eUtBiHd57rUDtAx2iPnEj6kc1hZTHefZvA==

    Do you have a fix for this? We do have a Stackpath integration

    The page I need help with: [log in to see the link]

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

    (@vmarko)

    Hello @seoservicesla

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Your website is hosted on Amazon CloudFront and the 502 ERROR is coming from the host and it’s not related to the W3 Total Cache plugin.
    Most likely the issue is with the invalid certificate chain. Please check this AWS article for more information and also contact your hosting provider for more assistance with this.
    Thanks!

    Thread Starter seoservicesla

    (@seoservicesla)

    lineups.com/articles wordpress install with the W3TC plugin is a reverse proxy and hosted on Liquid Web.

    Lineups.com is hosted on AWS.

    The 502s are displaying during image uploads and images are not hosted on AWS. This is how we determined the 502 errors are coming from W3TC.

    Thoughts?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @seoservicesla

    Thank you for the information. while I understand your perception, this means that uploading the images is only triggering the issue and as the 502 is coming directly from the AWS you should address the issue to them.
    Those 502 errors are not coming from W3TC.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘502 Cloudfront Errors’ is closed to new replies.