An error occurs in Jetpack 8.4.2 and I cannot set it!

Hi there,

We’re seeing that error because xmlrpc.php is now reported as not found.

It should be available in one of these locations:

https://www.senris.com/wp302ja/xmlrpc.php
https://www.senris.com/xmlrpc.php

What is the install path for WordPress? Misconfiguration could be the cause of this error.

Let us know.

Thanks,

Hello darnelldibbles,

The installation path of WordPress is as follows.

https://www.senris.com/wp302ja/xmlrpc.php

Above file has been existed before.

Previous versions of Jetpack worked fine, but recent versions of Jetpack are behaving strangely.

• This reply was modified 4 years, 7 months ago by Senri Miura.

We’re being blocked from accessing https://www.senris.com/wp302ja/xmlrpc.php which Jetpack requires to function.

Unfortunately, blocking XML-RPC is not a great solution for fighting security risks. It’s akin to selling your car because you don’t want it to be stolen.

Your site’s XML-RPC file is kind of like a communication gateway to your site. Jetpack, the WordPress Mobile Apps, and other plugins and services will use this file to communicate to your site. If this is blocked, you will have other issues pop-up down the road for the same reasons.

If you are using any security plugins, please try connecting with those temporarily deactivated. If you don’t have any, or if that didn’t work, I would suggest contacting your hosting provider and asking them to unblock your site’s XML-RPC. The most popular hosting providers out there have managed to find other ways to protect their servers without having to hinder your site and your ability to use services with your WordPress site.

I don’t need such templating support.

Even if I removed the block to https://www.senris.com/wp302ja/xmlrpc.php, the bug of Jetpack was not improved, so I asked.

In the definition of .htaccess,

# Accept xmlrpc.php
<FilesMatch “xmlrpc.php”>
Allow from all
</ FilesMatch>

However, I got an error in Jetpack settings.

At the time of your indication, the following definitions were used.

# XML-RPC access restricted, Automattic (Jetpack) allowed
<Files xmlrpc.php>
Order Deny, Allow
Deny from all
# IP address you want to allow
# Allow from XXX.XXX.XX.XX
Allow #Automattic
Allow from 192.0.64.0/18
</ Files>
#END XML-Restrict access to RPC, allow Automattic (Jetpack)

It is not blocked as it can be accessed by Jetpack crawlers.

If the meaningless support continues, we will uninstall the bug pack plugin called Jetpack.

The IP range you allowed does not cover all of of our IPs.

If you would like to continue to only offer XML-RPC access by whitelisting IP addresses, you will need to whitelist these IP addresses:

122.248.245.244
54.217.201.243
54.232.116.4

and this range: 192.0.64.0/18

Please note that we are constantly adding new hardware to our network to keep up with demand on our services. This means that these IP addresses could change (or be added to) at any time, and is yet another reason for why we discourage restricting XML-RPC access to specific IP addresses only.

I understand the IP range used by Automatic.

But, your answer is totally meaningless.
Even if .htaccess is set to the following, it does not work at all with the latest version of Jetpack.
Now, it doesn’t matter what your IP address is.

# Accept xmlrpc.php
<FilesMatch “xmlrpc.php”>
Allow from all
</ FilesMatch>

Currently, .htaccess is set to the above setting, but Jetpack and WordPress can not be linked, so Jetpack is disabled.

If this situation persists, I think uninstall Jetpack because it could use other plug-in instead of Jetpack.

• This reply was modified 4 years, 7 months ago by Senri Miura.
• This reply was modified 4 years, 7 months ago by Senri Miura.

P.S.

Currently, my site already has replaced all features used in Jetpack with other plugins. All plugins except Jetpack are working normally.
Only Jetpack does not work properly.
Thus, if the next Jetpack update doesn’t fix the bug, we’ll uninstall Jetpack completely.

• This reply was modified 4 years, 7 months ago by Senri Miura.
• This reply was modified 4 years, 7 months ago by Senri Miura.
• This reply was modified 4 years, 7 months ago by Senri Miura.

Hello James,

I just enabled Jetpack again and moved to the configuration process, and this time I was able to set up safely without errors.

My site health status has also changed to good, and there are no fatal errors.
I didn’t change anything on this server, so maybe there was a problem with the server side of Automatic.

For the time being, this issue is resolved, so this thread is closed and OK.
Thankfully, I didn’t have to uninstall Jetpack.

Thank you very much.

Regards,
Senri Miura

Supplement:

The following email has received from a Jetpack engineer regarding the matter I was inquiring this morning.

It seems that the server side of Jetpack handled the trouble.
Note that the “403 Forbidden” error is because I was temporarily disabling the Jetpack plugin.
Now it works fine as follows:

https://www.senris.com/wp302ja/xmlrpc.php?for=jetpack
↓
XML-RPC server accepts POST requests only.

From Jetpack Engineer
　　↓
Apr 17, 17:59 UTC
Senri,

Thanks for the extra information – I updated Jetpack to know that your Site URL is https://www.senris.com/wp302ja.

That got the xmlrpc.php working fine: https://www.senris.com/wp302ja/xmlrpc.php?for=jetpack
However, when jetpack actually tries to connect to it, we’re still getting a “403 Forbidden” error. I’m assuming it has to do with a rule in your custom .htaccess, or perhaps a security system on your host.

At this point, I would recommend reaching out to your webhost to see if they are able to check their PHP error logs to find out where the 403 errors are happening, and perhaps to start over with a new, clean, default .htaccess.

Please let us know the results of this troubleshooting and we can go from there. Thanks!

* Omitted below

• This reply was modified 4 years, 7 months ago by Senri Miura.