Plugin Support
Bruce (a11n)
(@bruceallen)
Happiness Engineer
Hi @prorm
It looks like there is some security on your server, either a plugin, or something your host is using which is preventing Jetpack from connecting to the XMLRPC file.
This is the error we see:
HTTP/1.1 409 Conflict
Date: Tue, 16 Mar 2021 19:14:25 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 83
Connection: close
Server: Apache/2
Age: 0
<script>document.cookie = “humans_21909=1”; document.location.reload(true)</script>
I’d suggest contacting your hosting provider and ask them to check their security logs for any blocked requests to the /wordpress/xmlrpc.php file on your site, using the Jetpack by WordPress.com
user agent.
If they only offer XML-RPC access by whitelisting IP addresses, then they will need to whitelist the IP addresses listed here:
https://jetpack.com/support/hosting-faq/#jetpack
Please note that these IP addresses could change (or more could be added) at any time. For that reason, we recommend your host uses the machine-readable versions of these IP ranges in JSON or plain text format to automate configuration changes on their systems.
Thread Starter
prorm
(@prorm)
Hi,
They do not see any issues in their logs.
Regards,
Juan
Hi Juan
The plain xmlrpc.php file is working ok, but Jetpack uses xmlrpc.php?for=jetpack
for its requests, and that is showing a 406 (not acceptable) error.
Please ask your host to check that url and advise on why that request is being blocked.
Thanks!
Thread Starter
prorm
(@prorm)
Hi Dan,
They ask for the server requirements of Jetpack to make it work fine and run it correctly.
The strange situation is that was running fine until middle of last week.
Regards
Hi @prorm,
It is indeed a strange situation. We have looped our developers in to do more testing at our end.
Meanwhile, you can report those specific errors to your host:
– http://central.com.uy/xmlrpc.php?for=jetpack
is returning a “406 Not Acceptable” error
– http://central.com.uy/xmlrpc.php
is returning an “HTTP/1.1 409 Conflict” error.
In terms of server requirements, we’d need all our IPs range to be fully whitelisted.
I’d also suggest asking your hosting provider 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.
We’ll keep you posted on anything we will find at our end.
Let me know what you find out, thanks!
Thread Starter
prorm
(@prorm)
Hi,
They whitelisted your IPs. May you check now please?
I disconnected from Jetpack and reconnected under wp-admin and the critical error still shows.
Regards
Hi @prorm,
Thanks for the follow-up, and sorry for the delay in getting back to you.
I checked the connection again, and I noticed another couple of different errors in the connection, all still related to your xmlrpc.php file.
If you check that one for Jetpack, you will notice that there is a 406 Not Acceptable error which makes me think it could be related to a Mod_Security issue.
We’re aware of a recent conflict between mod_security and Jetpack on sites that are hosted with your hosting provider. We are working directly with the host to get to the bottom of this issue and I’ve made a note to let you know when that issue has been resolved.
I don’t have a timeline on when we may see a resolution on this issue, but we’re working hard with the hosting provider to get to the bottom of this. Once we have a resolution, we’ll reach out with the next steps.
Please let me know if you have any further questions or doubts, and we’re happy to assist you.
Thread Starter
prorm
(@prorm)
new Jetpack version didn´t solve the problem.
Thread Starter
prorm
(@prorm)
All is working fine today!!
Thanks for confirming! The issue appears to be resolved now in most cases. Let us know if you have any more trouble.