Critical error (even with all plugins deactivated)

Hi @tracyrosen

While your site is publicly accessible, we cannot access your site’s XML-RPC file:

https://DOMAIN.COM/xmlrpc.php

This file is used by Jetpack and other plugins and apps to connect to your site. It must return the following message:

XML-RPC server accepts POST requests only.

You can see a working example here:

https://jetpack.com/xmlrpc.php

Since your site returns a 503 error for this page, I would recommend that you check the following:

1) 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 WordPress” button.

2) 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.

3) 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:

https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reconnecting-jetpack

I rely on Jetpack for subscriptions (which I will need to try to get to resubscribe since I had to delete the plugin… right?). The blog is used to send newsletters to our network. I use 7 other plugins, but even when I deactivated all of the plugins and tried to install Jetpack, I received the critical error message once again.

We have your stats and subscriber information safely stored on the WordPress.com side. Once the Jetpack connection is restored we can get those back for you!

Hi and thanks for your response – that is great to know about the stats and subscriber info!

The xmlrpc.php file is there with permissions set to 0644, like all of the other php files (this was likely a default, I have not changed anything relating to permissions)

There doesn’t seem to be anything in the .htaccess file related to it.

No security plugins.

I was able to activate jetpack on the 2nd site yesterday afternoon (an addon domain at fnaesc-cspnea.org ). This was after I had removed and reinstalled WordPress. Since it is accessible there but not on the main domain, I don’t think the host is blocking anything.

Earlier I said I hadn’t changed anything related to permissions BUT I did upgrade the PHP to the latest version from a deprecated one. Could that have affected things?

Thanks again for your help!

I just noticed that the add-on domain also shows a 404 page when I go to fnaesc-cspnea.org/xmlrpc.php but in this case, I was able to activate jetpack without getting a critical error. Strange. And this is also the case on other blogs I have on different servers (but with same hosting company). Ex: leadingfromtheheart.org

• This reply was modified 2 years, 5 months ago by tracyrosen.

Hi @tracyrosen

An inaccessible XML-RPC endpoint doesn’t cause a critical error, but it does influence the Jetpack connection since it’s an essential backbone of a solid communication between your website and our servers to use the Jetpack features.

I’ve tried to browse your XML-RPC endpoint again, and I was greeted with a “forbidden to access” page, which seems to be implemented by cPanel.

To resolve this, I’d highly suggest you reach out to your hosting provider and link them to your XML-RPC endpoint page and request that they allow access to that one so that Jetpack can send its requests there; they can also whitelist our IP ranges for that:

https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

Hello,
I contacted my hosting provider with all of the info you gave me. This was the response they gave me:

Our developer has fixed this issue with XML-RPC.
It was found that the jetpack plugin at installations caused a conflict by memory, not by the conflict with xmlrpc, in the same way the permission was added so that the xmlrpc was not accessible,

In any case, Jetpack isn’t causing a critical error anymore, and the xml-rpc endpoint page is no longer showing an error page either, which is good!
Thanks for your assistance,
Tracy

Hey there,

The Jetpack connection for the above mentioned site is now looking good and you can also check this here: https://jptools.wordpress.com/debug/?url=https://YOUR-SITE-NAME.org

Let me know if you are having any other issues?