Monitor does not send alerts when homepage is cached

  • Hi, when our provider is down but the litespeed cache is still running and serving cached content, Jetpack’s Monitor module does not send any alert.

    This means the site can be unavailable to either connected accounts (admin/author) or to visitors that otherwise get served non-cached content or try to place a Woocommerce order. All without the alert being sent…

    I suppose it is because of the cached homepage that is still accessible? Is there a way to get Monitor to send an alert if the back-end is down? Or make it check for responses via xmlrpc or with a designated query string parameter to circomvent caching?

    Thanks for any thought on this…

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hello there – Jetpack Monitor checks your site every five minutes to see if it is accessible. If your site loads, it won’t trigger a notice that your site is down. In your case, I think it is not notifying you because the LiteSpeed cache is serving cached content and Jetpack thinks your site is up while it is down from your hosting.

    However, I will check once with the team on how it works exactly behind and will provide you more info if the behavior can be changed.

    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    Hi Animesh, that is what I suspect as well. If only an “external” polling of the homepage is possible, it could be possible the circumvent caching by adding a request parameter to the polling URL.

    Either a unique string like a Unix timestamp /?1704018923 or an identifiable one like /?nocache or /?monitor=jetpack so that it can be added to the exclusion list in any caching solution on the site host/server side…

    Anyway, just a suggestion. Thanks for your response ??

    Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hello @ravanh – I was talking to our team and checking the LiteSpeed cache description I can see that it has a feature to:

    Exclude from cache by URI, Category, Tag, Cookie, User Agent

    So you should be able to exclude cache for?Jetpack Monitor?polling if you exclude Monitor’s?User Agent?jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hello?@ravanh,

    I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!

    Hi @bizanimesh that seems like a good solution. So I add the full jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com) or only jetmon/1.0 to the User Agent exclude list?

    Plugin Contributor Dan (a11n)

    (@drawmyface)

    Hi Rolf

    The user agent used by Jetpack Monitor is?jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com). In the LiteSpeed Cache settings, you should add the entire user agent string to the “Exclude from cache by User Agent” section. This means including?jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)?in your LiteSpeed Cache exclusion settings, not just?jetmon/1.0. This will help ensure that caching recognizes the specific Monitor agent and does not serve cached content in response to its checks.

    Thank you!

    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    Thanks Dan, that’s very clear ??

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Monitor does not send alerts when homepage is cached’ is closed to new replies.