The Jetpack server was unable to communicate with your site [HTTP 405]

  • Resolved wabetainfo

    (@wabetainfo)


    3 years ago

    Hi!

    I use Jetpack since more than 3 years and I never experienced an issue… but the day has come.
    At first, when visiting the Jetpack tab, I have noticed something wrong about cookies check failed. I tried to reconnect but it always said this error. So I tried to disable all plugins, but no luck. I tried to reinstall and I see a different error: The Jetpack server was unable to communicate with your site https://wabetainfo.com [HTTP 405]. I do not know why this is happening and I cannot use Jetpack anymore. Please help me understand what’s happening. My host is not blocking connections to wordpress.com, so it is not the issue. I didn’t update my plugins today and I’ve also tried to restore an old backup.

    In addition, my host is not blocking the xmlrpc.php file, and they are not blocking any IP address from Jetpack. In fact, https://wabetainfo.com/xmlrpc.php says “XML-RPC server accepts POST requests only.”

    EDIT: I just tried https://ratelimit.rudyfaile.com and I see this (note that I don’t have any security plugin that may limit xml-rpc):

    Request #1 | Server Response: 403 Forbidden
Request #2 | Server Response: 403 Forbidden
Request #3 | Server Response: 403 Forbidden
Request #4 | Server Response: 403 Forbidden
Request #5 | Server Response: 403 Forbidden
Request #6 | Server Response: 403 Forbidden
Request #7 | Server Response: 403 Forbidden
Request #8 | Server Response: 403 Forbidden
Request #9 | Server Response: 403 Forbidden
Request #10 | Server Response: 403 Forbidden
Request #11 | Server Response: 403 Forbidden
Request #12 | Server Response: 403 Forbidden
Request #13 | Server Response: 403 Forbidden
Request #14 | Server Response: 403 Forbidden
Request #15 | Server Response: 403 Forbidden
Request #16 | Server Response: 403 Forbidden
Request #17 | Server Response: 403 Forbidden
Request #18 | Server Response: 403 Forbidden
Request #19 | Server Response: 403 Forbidden
Request #20 | Server Response: 403 Forbidden
Request #21 | Server Response: 403 Forbidden
Request #22 | Server Response: 403 Forbidden
Request #23 | Server Response: 403 Forbidden
Request #24 | Server Response: 403 Forbidden
Request #25 | Server Response: 403 Forbidden
Request #26 | Server Response: 403 Forbidden
Request #27 | Server Response: 403 Forbidden
Request #28 | Server Response: 403 Forbidden
Request #29 | Server Response: 403 Forbidden
Request #30 | Server Response: 403 Forbidden
Request #31 | Server Response: 403 Forbidden
Request #32 | Server Response: 403 Forbidden
Request #33 | Server Response: 403 Forbidden
Request #34 | Server Response: 403 Forbidden
Request #35 | Server Response: 403 Forbidden
Request #36 | Server Response: 403 Forbidden
Request #37 | Server Response: 403 Forbidden
Request #38 | Server Response: 403 Forbidden
Request #39 | Server Response: 403 Forbidden
Request #40 | Server Response: 405 Method Not Allowed
Request #41 | Server Response: 405 Method Not Allowed
Request #42 | Server Response: 405 Method Not Allowed
Request #43 | Server Response: 405 Method Not Allowed
Request #44 | Server Response: 403 Forbidden
Request #45 | Server Response: 405 Method Not Allowed
Request #46 | Server Response: 405 Method Not Allowed
Request #47 | Server Response: 405 Method Not Allowed
Request #48 | Server Response: 405 Method Not Allowed
Request #49 | Server Response: 405 Method Not Allowed
Request #50 | Server Response: 405 Method Not Allowed
    • This topic was modified 3 years ago by wabetainfo.
    • This topic was modified 3 years ago by wabetainfo.
    • This topic was modified 3 years ago by wabetainfo.
    • This topic was modified 3 years ago by wabetainfo.
    • This topic was modified 3 years ago by wabetainfo.
    • This topic was modified 3 years ago by wabetainfo.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @wabetainfo –

    The 403 and 405 errors indicate that something is indeed blocking our ability to communicate with your site via XML-RPC. Your server doesn’t allow POST requests to XMLRPC.

    As a next step, you will want to check with your host to make sure that they allow POST requests to XMLRPC. Sharing the results of the 403/405 results may help them pinpoint the issue.

    Thread Starter wabetainfo

    (@wabetainfo)

    Thanks @lastsplash for your reply. I share the solution here so it may help other people that will experience a similar issue.
    I’ve contacted my host sharing the details about the 403/405 errors. They forced cache on my website since it used a lot of resources on their server due to an error of a plugin. Since my website used cache, POST requests were blocked even if I could open the xmlrpc.php page. They disabled the cache and it works again. Thanks!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hello @wabetainfo,

    I did another round of tests on your Jetpack site to confirm all is up and running beautifully now – you should be all set!

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The Jetpack server was unable to communicate with your site [HTTP 405]’ is closed to new replies.