502 Problem after upgrading to WP4 and W3 Total Cache

  • Had this problem before when upgrading when WP4 came out and went back to WP3, because I didn’t have the time to look for a solution.
    WP3 and up-to-date W3 Total Cache at the time: everything works fine
    Upgrade to most recent WP version and upgrade all plugins. Homepage and most articles show, but some articles display

    502 Bad Gateway

nginx/1.4.6 (Ubuntu)

    When I look in the error-log, I find this:

    2015/06/21 11:12:15 [error] 2549#0: *111218 readv() failed (104: Connection reset by peer) while reading upstream, client: 83.134.160.135, server: blog.johan-mares.be, request: "GET /skeptic/ervin-laszlo-flying-under-the-skeptic-radar/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "blog.johan-mares.be", referrer: "https://blog.johan-mares.be/"

    When I turn off W3 Total Cache, the pages that previously returned the 502 error, display normally, but still the same error message is logged.

    Summary: some pages when requested add a line to the nginx error.log file for that site, but display as intended with W3 Total Cache turned off and display a 502-page with W3 Total Cache turned on.
    I looked and have found those error messages in yesterday’s log-file. So, why would some pages give those errors and most not. Why did it became a problem after upgrading?

Viewing 1 replies (of 1 total)
  • Thread Starter johanm

    (@johanm)

    Keeping fingers crossed, but problem seems solved by upgrading from Thesis 1.8.5 to 1.8.6 theme.
    As to why certain pages displayed correctly and others not …?
    Pages display correctly and no longer “Connection reset by peer” errors in log files. Gonna keep an eye on it.

Viewing 1 replies (of 1 total)
  • The topic ‘502 Problem after upgrading to WP4 and W3 Total Cache’ is closed to new replies.