I have a WordPress site running on OpenLiteSpeed, and accessing XMLRPC with cURL like:
curl --data @hello.txt https://gateblogs.com/xmlrpc.php
with the correct info in hello.txt, returns:
<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
<params>
<param>
<value>
<string>Hello!</string>
</value>
</param>
</params>
</methodResponse>
but, Jetpack Debugger gives me a Communication error. I don’t get this because XMLRPC obviously works, and Jetpack worked with Apache, so I know none of my plugins are blocking it.
I also used:
curl -A ‘Jetpack by WordPress.com’ -is -H ‘Content-Type: text/xml’ --data ‘<?xml version=“1.0”?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>’ ‘https://gateblogs.com/xmlrpc.php’ && echo
Apache(what works) returned: 0; path=COOKIEPATH Set-Cookie: QnKVvgyjBb=e4x5FOl1S%40; expires=Wed, 28-Mar-2018 15:06:28 GMT; Max-Age=3600; path=COOKIEPATH X-LiteSpeed-Cache-Control: no-cache Vary: Accept-Encoding Expect-CT: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct” Server: cloudflare CF-RAY: 402aa831dc789248-EWR
<?xml version=“1.0” encoding=“UTF-8”?> <methodResponse> <params> <param> <value> <string>Hello!</string> </value> </param> </params> </methodResponse>
Litespeed returned: Set-Cookie: c_uINfQa=FEsjKuzn; expires=Wed, 28-Mar-2018 15:07:35 GMT; Max-Age=3600; path=COOKIEPATH Set-Cookie: QnKVvgyjBb=e4x5FOl1S%40; expires=Wed, 28-Mar-2018 15:07:35 GMT; Max-Age=3600; path=COOKIEPATH X-Litespeed-Cache-Control: no-cache Expect-CT: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct” Server: cloudflare CF-RAY: 402aa9efd9a791a0-EWR
<?xml version=“1.0” encoding=“UTF-8”?> <methodResponse> <params> <param> <value> <string>Hello!</string> </value> </param> </params> </methodResponse>
The only difference I see is the second Set-Cookie for Litespeed
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi @realNerdOfLinux,
I believe the answer is a bit easier than what you are trying to do. Are you sure Jetpack has access to your server and especially this file?
I’ll recommend to first allow access to the file. To do so, open your .htaccess file in your website
<Files xmlrpc.php>
order deny,allow
allow from all
</Files>
If you don’t want to allow access to the whole world, you can allow just JetPack’s IP addresses. To do you’ll just need to do the following
<Files xmlrpc.php>
order deny,allow
deny from all
allow from XXX.XXX.XXX.XXX
allow from XXX.XXX.XXX.XXX
allow from XXX.XXX.XXX.XXX
</Files>
You’ll need to change XXX.XXX.XXX.XXX with Jepack’s IP address.
The other solution might be just allowing the JetPack’s IP addresses in your server’s Firewall.
Regards, KDSys
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.