Support » Plugin: Jetpack by WordPress.com » Broke my site then didn’t tell me site was down

  • Resolved KD Sarge

    (@sargemarcori)


    I’ve had at least a hundred emails from JetPack over the years, telling me my site was down when it wasn’t. Then when something installed by JetPack–Advanced Cache–breaks my site to blank white with a couple errors on it (complaining it can’t load Super Cache when i don’t even have that installed!)…? Not a peep out of JetPack.

    Just a mite annoying, that.

    If this happens to you and you can’t get into your admin (I couldn’t,) go into your CPanel, File Manager, and in folder WP-Content, rename the file advanced-cache.php.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support fresatomica

    (@fresatomica)

    Hi there!

    I’d love to look into this for you.

    Could you please let me know your site’s address and provide more details on the error that caused your site to crash?

    Also, bear in mind that you can disable the Jetpack Monitor at any moment so you won’t receive emails every time there’s some issue on your site. You can read more about that here:
    https://jetpack.com/support/monitor/

    You can also reach us for support at

    https://jetpack.com/contact-support/

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    Just a quick note here, advanced-cache.php is not installed by Jetpack, but it is installed by WP Super Cache (and many other caching plugins).

    KD Sarge

    (@sargemarcori)

    Hi, fresatomica. The problem isn’t that I don’t want notified when my site has issues. The problem is I’ve gotten tons of false alarms, but the one time my site was actually down, I was not notified.

    The other problem, of course, would be if JetPack was how the file in question got onto my site. According to a wordpress.org support forum post I can’t find now, that’s where it came from.

    Here’s the site. http://turtleduckpress.com/wordpress/

    Here is the text of the errors.

    Warning: include_once(/home1/sporker1/public_html/wordpress/wp-content/plugins/wp-super-cache/wp-cache-phase1.php): failed to open stream: No such file or directory in /home1/sporker1/public_html/wordpress/wp-content/advanced-cache.php on line 14
    
    Warning: include_once(): Failed opening '/home1/sporker1/public_html/wordpress/wp-content/plugins/wp-super-cache/wp-cache-phase1.php' for inclusion (include_path='.:/opt/php70/lib/php') in /home1/sporker1/public_html/wordpress/wp-content/advanced-cache.php on line 14
    
    Warning: Cannot modify header information - headers already sent by (output started at /home1/sporker1/public_html/wordpress/wp-content/advanced-cache.php:14) in /home1/sporker1/public_html/wordpress/wp-includes/pluggable.php on line 1265
    
    Warning: Cannot modify header information - headers already sent by (output started at /home1/sporker1/public_html/wordpress/wp-content/advanced-cache.php:14) in /home1/sporker1/public_html/wordpress/wp-includes/pluggable.php on line 1268
    

    That’s very interesting, James Huff, considering I don’t have WP Super Cache or any other caching plugins installed, let alone active. Anti-Spam Bee, Cryout Serious Theme Settings, JetPack, WP Broken Link Status Checker, are the only plugins.

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    If your hosting provider has any built-in caching, the file could also be a part of that.

    But, if you aren’t using any caching, you can definitely the file. It definitely didn’t come from Jetpack though.

    When Jetpack Monitor checks your site, we ping your site’s homepage (via a HTTP HEAD request) every five minutes.

    We tentatively mark your site as down if the HTTP response code is 400 or greater, which indicates either a permissions error or a fatal code error is prohibiting your site from appearing to visitors, or we see more than 3 300-series redirects, suggesting a redirect loop, or if your site fails to respond within 20 seconds.

    Once it is tentatively marked down, we then spin up two separate servers in geographically different locations from a third-party vendor to ensure the problem is not isolated to our network or the location of our primary datacenter.

    If all three checks fail, we mark the site as down and notify you. We’ll continue to check the site and once we have agreement it is back online, we’ll send you the all-clear notice.

    So, if your site was still returning an HTTP 200 header in the errorred stated, we wouldn’t have marked it as offline.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.