jetpack your website is offline

same problem for me .. I can’t access to my stats and I’ve desactivate the mail for the moment …

I have this bug since the last update

Hello @olikanagold77,

Thanks for your patience and for bearing with us; we’re working on a massive backlog of support requests at this time, and we generally answer in the order received.

It looks like you received email notifications using our Monitor feature. Jetpack Monitor checks your site every five minutes to see if it is accessible. If your site is slow to load, it could trigger a notice that your site is down. We also send a follow-up email letting you know how long your site was down or inaccessible.

I checked the error you sharewd (thanks for that!) and that’s related to a possible server-side setting that disabled the Jetpack access, or alternatively it shows DNS issues. In both cases, you need to check your host to have it addressed.

Currently, there’s no way to adjust the time that Monitor checks your site – it’s either on or off. If the frequency of notices is bothersome, you can always disable that module on the site by following the instructions here:
https://jetpack.com/support/monitor/

Lastly, I see that the Jetpack communication is not working as expected, so you want to fix that, too, in order to have everything in order and better address the Monitor-related error that Jetpack flagged.

It looks like your site returns a 404 error for the xmlrpc.php page. I would recommend that you check the following:

• Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then click the “Reinstall” button.
• Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
• Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

Once we are able to access your site’s xmlrpc.php file, please try to reconnect your site:

Let me know how you get on!

****

@oufmilo: please open your own thread if you need help, thanks!

Thank you so much for your answer.

I have checked everything you told me:

• Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then click the “Reinstall” button.

Yes, the file is there.

• Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
  This is my HTACCESS file, I think nothing is not allowing access to the xmlrpc/hp file.

BEGIN LSCACHE LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block!

RewriteEngine on
CacheLookup on
RewriteRule .* – [E=Cache-Control:no-autoflush]
RewriteRule .litespeed_conf.dat – [F,L] marker ASYNC start

RewriteCond %{REQUEST_URI} /wp-admin/admin-ajax.php
RewriteCond %{QUERY_STRING} action=async_litespeed
RewriteRule .* – [E=noabort:1] marker ASYNC end marker MOBILE start

RewriteCond %{HTTP_USER_AGENT} Mobile|Android|Silk/|Kindle|BlackBerry|Opera\ Mini|Opera\ Mobi [NC]
RewriteRule .* – [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+ismobile] marker MOBILE end marker CACHE RESOURCE start

RewriteRule wp-content/./[^/](responsive|css|js|dynamic|loader|fonts).php – [E=cache-control:max-age=3600] marker CACHE RESOURCE end marker FAVICON start

RewriteRule favicon.ico$ – [E=cache-control:max-age=86400] marker FAVICON end marker WEBP start

RewriteCond %{HTTP_ACCEPT} “image/webp”
RewriteRule .* – [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
RewriteCond %{HTTP_USER_AGENT} iPhone.Version/(\d{2}).Safari
RewriteCond %1 >13
RewriteRule .* – [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp] marker WEBP end marker DROPQS start

CacheKeyModify -qs:fbclid
CacheKeyModify -qs:gclid
CacheKeyModify -qs:utm*
CacheKeyModify -qs:_ga marker DROPQS end LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! END LSCACHE BEGIN NON_LSCACHE LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! marker BROWSER CACHE start

ExpiresActive on
ExpiresByType application/pdf A31557600
ExpiresByType image/x-icon A31557600
ExpiresByType image/vnd.microsoft.icon A31557600
ExpiresByType image/svg+xml A31557600

ExpiresByType image/jpg A31557600
ExpiresByType image/jpeg A31557600
ExpiresByType image/png A31557600
ExpiresByType image/gif A31557600
ExpiresByType image/webp A31557600

ExpiresByType video/ogg A31557600
ExpiresByType audio/ogg A31557600
ExpiresByType video/mp4 A31557600
ExpiresByType video/webm A31557600

ExpiresByType text/css A31557600
ExpiresByType text/javascript A31557600
ExpiresByType application/javascript A31557600
ExpiresByType application/x-javascript A31557600

ExpiresByType application/x-font-ttf A31557600
ExpiresByType application/x-font-woff A31557600
ExpiresByType application/font-woff A31557600
ExpiresByType application/font-woff2 A31557600
ExpiresByType application/vnd.ms-fontobject A31557600
ExpiresByType font/ttf A31557600
ExpiresByType font/otf A31557600
ExpiresByType font/woff A31557600
ExpiresByType font/woff2 A31557600 marker BROWSER CACHE end LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! END NON_LSCACHE o2s WpTiger Begin – Dont edit – Ne pas modifier – forceHttps Force le HTTPS

RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteCond %{HTTPS} !on
RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] o2s WpTiger End – Dont edit – Ne pas modifier – forceHttps BEGIN WordPress Les directives (lignes) entre ? BEGIN WordPress ? et ? END WordPress ? sont générées dynamiquement, et doivent être modifiées uniquement via les filtres WordPress. Toute modification des directives situées entre ces marqueurs sera surchargée.

RewriteEngine On RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress

• Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.
  I spoke with my host, is O2switch. They say nothing should block access to this file.

I just contacted my host, they will answer soon. It cannot be our plugins because it was working well. This is happening since we change our host, from CONTABO to O2switch.

Thanks again, hope we could find the solution,

Hi there, @olikanagold77,

If you see the file there via FTP, it’s possible that there is something that’s preventing the file from being published online as expected.

Upon contacting your host, have them check the xmlrpc.php file again, and ask them to make sure it displays okay with no 404 not found error in the page. You may need to turn off your caching plugin to see if it’s conflicting.

Keep us posted on how it goes!

I use litespeed cache. I see no diference when I turn if off.

The weird thing is that I can connect jetpack, but after 1 day in wordpress I always see the message “signature mismatch” and I have to reconnect it. I guess this is something to do with the mails that say that my website is offline..

Their answer:

I just disabled our security to test.
I still have a 404 on https://www.olikana.com/xmlrpc.php

This means that it is your site which blocks the request directly via security plugin or .htaccess for example.

We cannot act on this at our level.

Hey @olikanagold77,

Thanks for working this out with us and for acting as a bridge with your host. I can see the xmlrpc.php file now online, which is a progress.

The debug, however, still shows error, possible due to security blocks that your host should be able to unlock. Can you please circle back to them and have them disable security, firewall and caching tools/software?

You may want to share the following errors:

Action is missing from available XML-RPC methods

La requ\u00eate n’est pas correctement sign\u00e9e.","data":{"status":400}}

I hope it helps your host figure out what’s blocking the connection ??

Also, can you tell me more about the following?

I always see the message “signature mismatch” and I have to reconnect it. I guess this is something to do with the mails that say that my website is offline..

Can you share a screenshot of the error? You can share screenshots if that helps. You can create screenshots using something like Snipboard or Imgur and post the link here.

Same for the emails about your site being offline: do they come from Jetpack? What do they say in detail? Is there any error code you can share?

Thank you so much, we are in progress! You’ll go to heaven you know that?

My Host told me that they did not change anything, I don’t understand how the xmlrpc.php file can be now online but well ??

I have told my Host to do what you said, I’ll keep you updated.

For jetpack on wordpress, I can connect it but after few hour i see this message:

https://snipboard.io/BOK7r4.jpg

And also, I receive mails from jetpack every 3-4 hours that say this:

https://snipboard.io/ecxnXq.jpg

I’m sorry it’s in french !

Hello @olikanagold77,

I have very good news! Everything does seem to be working properly now. YAY! You can check the latest debug looking good:

https://jptools.wordpress.com/debug/?url=https%3A%2F%2Fwww.olikana.com%2F

I hope you’re not experiencing this issue anymore.

As for the email you receive about your site going online and offline intermittently, these are email notifications from our Monitor feature. Jetpack Monitor checks your site every five minutes to see if it is accessible. If your site is slow to load, it could trigger a notice that your site is down. We also send a follow-up email letting you know how long your site was down or inaccessible.

The error code shown in the email, xxxx/intermittent, means that the request timed out, or not responding after 10 seconds. This case is can be confusing because your site may actually be loading, it’s just really slow. Usually, those cases self-resolve, as slow speeds could be temporary that day or intermittent every day. I recommend reporting it to your host so they can address that at their end.

Currently, there’s no way to adjust the time that Monitor checks your site – it’s either on or off. If the frequency of notices is bothersome, you can always disable that module on the site by following the instructions here:
https://jetpack.com/support/monitor/

I hope that clarifies things! Let us know if we can help with anything related to the Jetpack plugin in the future!

it was working but now the debug tool shows an unknow error ??

I don’t understand why the xmlrpc file works now if we did not change anything.

This error with jetpack is driving me crazy uuuuhh

Sometimes it gives error, sometimes it says that everyting looks great ?? (the debug tool)

Hi there @olikanagold77,

I can see how this error can drive you crazy! I checked the debug again, and I was lucky enough to see it all green.

It sounds like it’s bit of hit and miss with the connection being very intermittent. The error you reported, however, points to a server issue so we can’t take any more actions than suggesting you to report that to your hosting provider. The Monitor’s intermittent error is another clue that leads to server’s issues as the root of the problem.

I am not happy to say this, but sometimes hosts don’t have enough resources to sustain connections like Jetpack’s, especially if they’re small hosts and servers are heavily shared. It might not be your host’s case, though!

Let me know if they can work something out about that! ??

This is the “very good information so specific” haha that I have in my log error in wordpress

I guess is jetpack.

anyway you’ll go to heaven, thanks a lot take care!

[21-Mar-2024 17:44:25 UTC] Connection refused
[21-Mar-2024 17:44:25 UTC] Connection refused
[21-Mar-2024 17:44:31 UTC] Connection refused
[21-Mar-2024 17:44:31 UTC] Connection refused
[21-Mar-2024 17:44:37 UTC] Connection refused
[21-Mar-2024 17:44:43 UTC] Connection refused
[21-Mar-2024 17:44:49 UTC] Connection refused
[21-Mar-2024 17:44:55 UTC] Connection refused
[21-Mar-2024 17:45:00 UTC] Connection refused
[21-Mar-2024 17:45:06 UTC] Connection refused
[21-Mar-2024 17:45:12 UTC] Connection refused
[21-Mar-2024 17:45:16 UTC] Connection refused
[21-Mar-2024 17:45:18 UTC] Connection refused
[21-Mar-2024 17:45:24 UTC] Connection refused
[21-Mar-2024 17:45:25 UTC] Connection refused
[21-Mar-2024 17:45:30 UTC] Connection refused
[21-Mar-2024 17:45:31 UTC] Connection refused
[21-Mar-2024 17:45:36 UTC] Connection refused
[21-Mar-2024 17:45:42 UTC] Connection refused
[21-Mar-2024 17:45:48 UTC] Connection refused
[21-Mar-2024 17:45:54 UTC] Connection refused
[21-Mar-2024 17:46:00 UTC] Connection refused
[21-Mar-2024 17:46:06 UTC] Connection refused
[21-Mar-2024 17:46:12 UTC] Connection refused
[21-Mar-2024 17:46:17 UTC] Connection refused
[21-Mar-2024 17:46:23 UTC] Connection refused
[21-Mar-2024 17:46:24 UTC] Connection refused
[21-Mar-2024 17:46:29 UTC] Connection refused
[21-Mar-2024 17:46:30 UTC] Connection refused
[21-Mar-2024 17:46:36 UTC] Connection refused
[21-Mar-2024 17:46:41 UTC] Connection refused
[21-Mar-2024 17:46:47 UTC] Connection refused
[21-Mar-2024 17:46:53 UTC] Connection refused
[21-Mar-2024 17:46:54 UTC] Connection refused
[21-Mar-2024 17:47:00 UTC] Connection refused
[21-Mar-2024 17:47:05 UTC] Connection refused
[21-Mar-2024 17:47:11 UTC] Connection refused
[21-Mar-2024 17:47:16 UTC] Connection refused
[21-Mar-2024 17:47:17 UTC] Connection refused
[21-Mar-2024 17:47:23 UTC] Connection refused
[21-Mar-2024 17:47:24 UTC] Connection refused
[21-Mar-2024 17:47:29 UTC] Connection refused
[21-Mar-2024 17:47:30 UTC] Connection refused
[21-Mar-2024 17:47:35 UTC] Connection refused
[21-Mar-2024 17:47:41 UTC] Connection refused
[21-Mar-2024 17:47:47 UTC] Connection refused
[21-Mar-2024 17:47:53 UTC] Connection refused
[21-Mar-2024 17:47:59 UTC] Connection refused
[21-Mar-2024 17:47:59 UTC] Connection refused
[21-Mar-2024 17:48:05 UTC] Connection refused
[21-Mar-2024 17:48:10 UTC] Connection refused
[21-Mar-2024 17:48:16 UTC] Connection refused
[21-Mar-2024 17:48:22 UTC] Connection refused
[21-Mar-2024 17:48:23 UTC] Connection refused
[21-Mar-2024 17:48:28 UTC] Connection refused
[21-Mar-2024 17:48:29 UTC] Connection refused
[21-Mar-2024 17:48:34 UTC] Connection refused
[21-Mar-2024 17:48:40 UTC] Connection refused
[21-Mar-2024 17:48:46 UTC] Connection refused
[21-Mar-2024 17:48:52 UTC] Connection refused
[21-Mar-2024 17:48:58 UTC] Connection refused
[21-Mar-2024 17:49:04 UTC] Connection refused
[21-Mar-2024 17:49:10 UTC] Connection refused
[21-Mar-2024 17:49:16 UTC] Connection refused
[21-Mar-2024 17:49:17 UTC] Connection refused
[21-Mar-2024 17:49:20 UTC] Connection refused
[21-Mar-2024 17:49:22 UTC] Connection refused
[21-Mar-2024 17:49:22 UTC] Connection refused
[21-Mar-2024 17:49:22 UTC] Connection refused
[21-Mar-2024 17:49:27 UTC] Connection refused
[21-Mar-2024 17:49:28 UTC] Connection refused
[21-Mar-2024 17:49:28 UTC] Connection refused
[21-Mar-2024 17:49:28 UTC] Connection refused
[21-Mar-2024 17:49:29 UTC] Connection refused
[21-Mar-2024 17:49:34 UTC] Connection refused
[21-Mar-2024 17:49:40 UTC] Connection refused
[21-Mar-2024 17:49:46 UTC] Connection refused
[21-Mar-2024 17:49:51 UTC] Connection refused
[21-Mar-2024 17:49:57 UTC] Connection refused
[21-Mar-2024 17:49:57 UTC] Connection refused
[21-Mar-2024 17:49:59 UTC] Connection refused
[21-Mar-2024 17:50:03 UTC] Connection refused
[21-Mar-2024 17:50:09 UTC] Connection refused
[21-Mar-2024 17:50:15 UTC] Connection refused
[21-Mar-2024 17:50:20 UTC] Connection refused
[21-Mar-2024 17:50:26 UTC] Connection refused
[21-Mar-2024 17:50:27 UTC] Connection refused
[21-Mar-2024 17:50:28 UTC] Connection refused
[21-Mar-2024 17:50:29 UTC] Connection refused
[21-Mar-2024 17:50:30 UTC] Connection refused
[21-Mar-2024 17:50:32 UTC] Connection refused
[21-Mar-2024 17:50:38 UTC] Connection refused
[21-Mar-2024 17:50:40 UTC] Connection refused
[21-Mar-2024 17:50:41 UTC] Connection refused
[21-Mar-2024 17:50:41 UTC] Connection refused
[21-Mar-2024 17:50:42 UTC] Connection refused
[21-Mar-2024 17:50:43 UTC] Connection refused
[21-Mar-2024 17:50:44 UTC] Connection refused
[21-Mar-2024 17:50:50 UTC] Connection refused
[21-Mar-2024 17:50:50 UTC] Connection refused
[21-Mar-2024 17:50:51 UTC] Connection refused
[21-Mar-2024 17:50:52 UTC] Connection refused
[21-Mar-2024 17:50:54 UTC] Connection refused
[21-Mar-2024 17:50:54 UTC] Connection refused

I think I just found something…

When I disable REDIS and I use MEMCACHED instead the errors “connexion refused” stop…

Now, I just need to be sure jetpack will stay connected anyway… That’s less sure…

I don’t know why I did not notice this before when i disabled litespeed…

Anyway I still had problems with jetpack even without litespeed I’ll keep you updated!

Hey @olikanagold77,

Good investigation here! Keep an eye on the connection, and if you need a replacement for the caching plugin, you can consider WP Super Cache: it is a free, low-maintenance plugin that’s 100% compatible with Jetpack. Give it a try and let know if that helps.