XML-RPC – Connection Failed – Error 200

Resolved

(@willc93)

When I check Site Health I get a TechBreakOut is not connected.: 200 error.

When I debug for the error, I get the following message:

XML-RPC is not responding correctly ( 200 )
It looks like XML-RPC is not responding correctly. Please make sure XML-RPC is turned on for your site and is set up to respond to all content types. You can test this yourself by running the following command from the command line:

curl -A 'Jetpack by WordPress.com' -d '<methodCall><methodName>demo.sayHello</methodName></methodCall>' https://techbreakout.com/xmlrpc.php
The answer should be:

<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
  <params>
    <param>
      <value>
      <string>Hello!</string>
      </value>
    </param>
  </params>
</methodResponse>

I do not understand what this means or what I need to do. I’ve found others with similar issues. I upgraded my PHP last year to 7.x for a mediawiki site so I need to keep the PHP upgraded.

What do I need to do to fix this error? I have access to my xmlrpc.php file. Do I need to make a change in there? If so where and how?

I can also reach out to my host…. what would I need to tell them?

The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)

Thread Starter willc93
(@willc93)

3 years, 9 months ago

Just got off chat with my Host, HostGator, and they are telling me to come back to Jetpack’s support.

I am on PHP 7.4. We lowered to PHP 5.4 and that broke my site (critical error), and put it at 7.0, but nothing changed so put it back to 7.4.

When I view my XML-RPC, I get:
XML-RPC server accepts POST requests only.

So I don’t think the issue is with XML-RPC. Another post I found was saying it was because old files are still reading the old PHP code. I’ve updated the code in my .htaccess file and that did not work. I changed it from:
<IfModule mime_module>
AddHandler application/x-httpd-ea-php70___lsphp .php .php7 .phtml
</IfModule>

to

<IfModule mime_module>
AddHandler application/x-httpd-ea-php70 .php .php7 .phtml
</IfModule>

Nothing changed. Still cannot connect.
Bruce (a11n)
(@bruceallen)

Happiness Engineer

3 years, 9 months ago
Hi @willc93

A couple of things here, first your site is connected to Jetpack, but using the “Alternate endpoint” – this occurs when Jetpack is unable to connect via XMLRPC.

When I visit https://yourdomain.com/xmlrpc.php in a browser I see:
```
 It appears you don't have
permission to access this page.
403 Error. Forbidden. 
```
The file needs to be publicly accessible. I’d suggest checking if you have any security plugins activated that might be blocking our requests. If not, try contacting your hosting provider and asking them to check their security logs to see if they are blocking or otherwise limiting incoming and outgoing connections over XML-RPC.

Jetpack uses this file to communicate with your site, but some hosts block connection requests to that file.

Our requests look like the following:

- File: https://yourdomain.com/xmlrpc.php
- User-agent header: Jetpack by WordPress.com
- IPs: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

Please ask them to allowlist the IP addresses listed above. Note that these IP addresses could change (or more could be added) at any time, which could break your connection to Jetpack. For this reason, we actually discourage allowing specific IPs, although with some hosts it may be the only option.

Also, if you visit http://yourdomain.com/ (not https) it loads a blank white page. This should redirect to the https version of your site.

Let us know how that goes.
- This reply was modified 3 years, 9 months ago by Bruce (a11n).
preux
(@preux)

3 years, 9 months ago

If you have CleanTalk you could try updating it to v5.182.2

Since August 4th there have been problems, but this update solved it.

MadHatter (a11n)
(@madhattersez)

3 years, 9 months ago

Hello, there.

It looks like you don’t have the CleanTalk plugin, but I do also see 403 Forbidden blocks.

I just noticed you’re using a plugin called “disable-xml-rpc,” so that’s probably the culprit if your host is not blocking it. Removing that plugin should allow us to connect.

Thread Starter willc93
(@willc93)

3 years, 9 months ago

Hi @madhattersez & @bruceallen,

I have downloaded the CleanTalk plugin and the issue still persists.

For the “diasable-xml-rpc” plugin, that was installed by my host and was installed after my post but before your replies. The issue is still there whether that plugin is enabled or disabled. I’ve gone ahead and deleted the plugin. When I go to sitename/xmlrpc.php I get the “XML-RPC server accepts POST requests only.” message, but I still cannot access Jetpack features.

In the WordPress app, I originally was able to log into a single Jetpack/Wordpress login that connected all my sites. That still slightly works… for whatever reason, it only shows 2 of my 3 sites, and I can only view stats. When I try to post, it fails, and I am unable to view/see any existing posts/pages or drafts.

After I created this thread, I was able to manually log in without using Jetpack, however, that only lasted about 12 hours before breaking. I am now unable to log in with that method now too.

Thread Starter willc93
(@willc93)

3 years, 9 months ago

Another update. My sites are now showing the below error when going to xmlrpc. I get this on sites that I hadn’t done anything to yet. I have three sites I am working on. I’ve only been messing with one, TechBreakOut, but now all my sites are having issues.

Not Acceptable!
An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.

TechBreakOut shows a 404 error though… and the debug shows no issues, but still I can’t connect.
The debug for my other two sites (sponsorhunter.com and activcode.com) show the 200 error still.

MadHatter (a11n)
(@madhattersez)

3 years, 9 months ago

Hello again,

Unfortunately, it looks like all three sites have the same issue:

https://sponsorhunter.com/xmlrpc.php?for=jetpack
https://activcode.com/xmlrpc.php?for=jetpack
https://techbreakout.com/xmlrpc.php?for=jetpack

The xmlrpc.php files linked above all lead to a blank page. At this point, something has altered those files or is blocking them. As long as the xmlrpc.php files are not working normally, Jetpack will be unable to connect to them.

It must return the following exact message:

XML-RPC server accepts POST requests only.

You can see a working example here: https://jetpack.com/xmlrpc.php

You’ll want to reach out to your webhost for these and have them get you a fresh, clean xmlrpc file and ensure that we are not being blocked access to them. For the best results, you could also have them allowlist the Jetpack IP ranges noted on this page:

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

Once you’ve spoken with them and you can visit each of those links and see the file being loaded properly, please let us and we’ll run some connection tests from our side.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘XML-RPC – Connection Failed – Error 200’ is closed to new replies.