Hi @atfpodcast
Thanks for reaching out. I took a look, and while your site is publicly accessible, we cannot access your site’s XML-RPC file:
https://www.abovethefirehouse.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://wp.cloud/xmlrpc.php
Since your site returns a blank page here, 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:
https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reconnecting-jetpack
If you want to learn more details about XML-RPC and how it interacts with Jetpack, you can check out our detailed guide here: https://jetpack.com/support/jetpack-and-xml-rpc
Hello,
‘I just looked ad I do see the file in my FTP. What do you mean by security plugins? My other sites work. It’s just this one.’I just looked ad I do see the file in my ftp. What do you mean by security plugins? My other sites work. It’s just this one.I added the /xmlrpc.php to my other sites and it shows the same message you showed.
Hi @atfpodcast
For security plugins, do you have any plugins that provide firewall services, like WordFence, or any plugins that scan your site?
You can also try temporarily disabling your other plugins and then see if the https://www.abovethefirehouse.com/xmlrpc.php page is loading correctly for your site after that. If it is, you can test enabling the other plugins one at a time to see when the xmlrpc file starts having trouble again, that will let you know which plugin is causing the issue.
If it still isn’t working with all the other plugins disabled, your best option would be to get in contact with your hosting provider to see if they are blocking access to the file. If they are, they can add the Jetpack IP address ranges to the server allowlist to make sure that Jetpack is able to connect. This page has the ranges that would need to be added:
https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/
No nothing like that. How do you mean scan my site?. Should I post my site health information? The host is not blocking it because it works on my other sites so I know that part is good. ;).
Something is blocking Jetpack from accessing your site’s XML-RPC file. That could be your web host blocking access, or a security or firewall plugin or service, such WordFence.
This is not something we can fix on our end, since the block is coming from somewhere else.
Please ask your web host to check their security logs for any blocked requests to the xmlrpc.php file on your site, using the Jetpack by WordPress.com user agent.
When you contact your web host, please also ask them to allow our IP addresses listed here: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/
Hi there, @atfpodcast,
It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!
Sorry I’ve been working. I seem to have found the issue. It seems to be the Realy Simple SSL plugin. Now I have to figure out where in this plugin its blocking because its fine in other sites.
Hey @atfpodcast – Thank you for sharing your findings with us. It’s good to hear that you’ve identified the plugin that may be causing the issue. In case you need help, you may contact the Really Simple SSL plugin team to help you finding the issue or if any setting in the Really Simple SSL plugin need to change to make it work with Jetpack.
