Title: 502 Cloudfront Errors
Last modified: August 10, 2020

---

# 502 Cloudfront Errors

 *  Resolved [seoservicesla](https://wordpress.org/support/users/seoservicesla/)
 * (@seoservicesla)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/502-cloudfront-errors/)
 * 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](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2F502-cloudfront-errors%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/502-cloudfront-errors/#post-13233130)
 * Hello [@seoservicesla](https://wordpress.org/support/users/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](https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cloudfront-connection-error/)
   for more information and also contact your hosting provider for more assistance
   with this. Thanks!
 *  Thread Starter [seoservicesla](https://wordpress.org/support/users/seoservicesla/)
 * (@seoservicesla)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/502-cloudfront-errors/#post-13233248)
 * 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](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/502-cloudfront-errors/#post-13233316)
 * Hello [@seoservicesla](https://wordpress.org/support/users/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.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

## Tags

 * [502 errors](https://wordpress.org/support/topic-tag/502-errors/)

 * 3 replies
 * 2 participants
 * Last reply from: [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * Last activity: [5 years, 10 months ago](https://wordpress.org/support/topic/502-cloudfront-errors/#post-13233316)
 * Status: resolved