Hello there, Maarten.
Do you mean the connection isn’t working randomly, or is the actual Jetpack plugin deactivated?
Right now, I see that Jetpack isn’t connected due to this error:
transport error - HTTP status code was not 200 (405)
A 405 error generally means that your server is blocking Jetpack’s connection. The best first step is to reach out to your webhost to have them check their PHP error logs to see what exactly is causing a 405 error. They should be able to locate the issue and possibly even fix it for you after finding the source.
Have them make sure that Jetpack is not getting blocked or limited or is prevented from accessing your xmlrpc.php file. For the best results, you could also have them whitelist the Jetpack IP ranges noted on this page:
https://jetpack.com/support/hosting-faq
If your actual Jetpack plugin is getting deactivated, then that is something you’ll want to speak to them about as well, as plugins being deactivated without you doing so is an odd occurrence and may be some sort of security feature on their side.
Once you’ve spoken with them, all blocks have been removed, and we are whitelisted, please let us know if you continue to have any other troubles. Thanks!
Hi there,
It has been more than one week since we have heard from you, so I’m marking this topic as resolved. But If you have any further questions or need some more help, you’re welcome to reply here or open another thread.
