getting false “Alert: -site- appears to be offline or unresponsive” emails

Wordpress 5.2.4
Jetpack version 7.7.3

Thanks for that info. You can see the typical causes of false downtime errors here:
https://jetpack.com/support/monitor/

Since the sites aren’t in production yet, if the issue is with redirects, you could consider just disabling monitoring until the sites are in production.

You could also have a look at server logs during supposed “downtime” to see if it’s blocking us.

If it doesn’t seem to be either of those things, let us know.

Hello, and thanks for your prompt reply.

I had checked your link and didn’t see anything that seemed at least on the surface to apply to my situation. I did a wget and didn’t see any redirects in the headers. The most recent email was at 1:16 MST this afternoon.

In my activity log on www.remarpro.com I don’t see any activity. I don’t really want to disable the monitoring since I want to get this figured out before I move production instances into this multisite AWS server.

One thing that came up as a warning in error_log: PageSpeed Serf fetch failure rate extremely high; only 0 of 18 recent fetches fully successful; is fetching working?

Could this be related?

Thank you.

I don’t see any Jetpack connection for https://www.unixguys.com:

https://jetpack.com/support/debug/?url=https://www.unixguys.com/

So I assume the errors are for the actual site/sites in your network? Can you share the addresses at which you currently have those connected to Jetpack so we can check if there’s any more details on our end why Jetpack might be thinking those sites are down?

If you don’t want to share the URLs here publicly, please open a ticket at https://jetpack.com/contact-support/?rel=support and refer to this thread.

One thing that came up as a warning in error_log: PageSpeed Serf fetch failure rate extremely high; only 0 of 18 recent fetches fully successful; is fetching working?

Could this be related?

It could be, in the sense that the same thing that’s causing PageSpeed fetches to your site to fail is also causing Jetpack Monitor’s requests to your site to fail.

You can see https://www.modpagespeed.com/doc/faq#warning-fetch-rate for details on what might be causing the PageSpeed errors. There’s also some suggestions in this thread I found on the Bitnami forums that might help.

See if you’re able to fix whatever is causing those errors. If you still get the Monitor errors at that point it would confirm it’s something else causing Monitor to think the site is down.

Hmmm, that’s weird about not seeing a jetpack connection, but I might be having an internal DNS/external DNS issue I will check on.

My email says:

Need help? No problem.

You can customize these alerts in your security settings.

Finally, I did yesterday see that same link you sent and disabled the bitnami banner in the lower right-hand corner to see if that makes a difference for the modpagespeed log messages.

Thanks for your reply.

Okay, that reference lead me to a Jetpack connection on our end, but it’s connected via an IP, not a domain, so it looks like you made that connection before you’d added a domain to your site. If I try to view the Jetpack debugger for that IP, it just redirects to the debug link for the domain which says that there isn’t any Jetpack connection active.

So let’s see if disconnecting and reconnecting Jetpack perhaps helps here – that should recreate the Jetpack connection at the domain you currently have assigned to the site.

To disconnect, go to WP-Admin ->Jetpack ->Dashboard, and click the Manage site connection link in the Connections section towards the bottom of that page.

Hello,

Thanks for the pointer. I unlinked and relinked my site from jetpack, and all seems well.

I haven’t received any false alarms in the last 2-3 days, and I’m not sure if it was the relinking, or the removing the bitnami admin link that did it. I’m going to let it go a couple more days to see for sure.

Thanks again.

Oh good… I’m glad that seems to have been the end of it. Enjoy your week, and if you hear more false alarms, let us know.