• Resolved hhfarmstead

    (@hhfarmstead)


    I was having an issue using the Woo app as it was unable to retrieve my data. After putting in a ticket, I followed the instructions on the troubleshooting page. Now, after removing Jetpack, I’m unable to reconnect it to my site. As a result, other plugins are not working either. HELP!

    I have done the done all of the following without resolve:
    – Ran the debug tool and get the following response: XML-RPC is not responding correctly ( 200 )
    – Checked my site health: Good
    – Checked my XML-RPC file at my website to make sure no spaces/empty lines were present
    – Ran the WordPress XML-RPC Validation Service: 1000004 We cannot find the XML-RPC Endpoint within the RSD document
    – Disabled all plugins
    – Changed theme to Twenty Twenty

    I have contacted my hosting company to ensure that it is enable and accepts connections of all kinds. They have assured me it is and it does.

    Any help would be greatly appreciated!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Anonymous User 3392934

    (@anonymized-3392934)

    Hey there, @hhfarmstead! Thank you for reaching out to us about this Jetpack connection issue.

    You didn’t provide a URL, so I’m assuming you’re referring to hilltophavenfarmstead.com.

    It looks like your site is including a PHP notice as part of XML-RPC’s output:

    
    <?xml version="1.0" encoding="UTF-8"?>
    <methodResponse>
      <params>
        <param>
          <value>
          <string>Hello!</string>
          </value>
        </param>
      </params>
    </methodResponse>
    <br />
    <b>Deprecated</b>:  Directive 'allow_url_include' is deprecated in <b>Unknown</b> on line <b>0</b><br />
    

    Specifically, this is the part that shouldn’t be there:

    
    <b>Deprecated</b>:  Directive 'allow_url_include' is deprecated in <b>Unknown</b> on line <b>0</b><br />
    

    This unexpected output breaks Jetpack’s connection.

    It looks like, under certain conditions, using cPanel to upgrade PHP might cause this error. I was able to find someone with a similar issue (and their resolution) here:

    https://ww.wp.xz.cn/support/topic/wordpress-does-not-work-on-php-above-7-1/#post-13353213

    If that doesn’t help out, please reach out to Bluehost. As your hosting provider, they are in a better position to troubleshoot a PHP notice:

    https://www.bluehost.com/contact

    Thank you! 🙂

    • This reply was modified 5 years, 7 months ago by Anonymous User 3392934.
    Thread Starter hhfarmstead

    (@hhfarmstead)

    Mark!

    First, thank you for responding so quickly. It doesn’t feel good to have my site and store down and I so appreciate you!

    I have been working with Bluehost to try to see if they would run the command that I found in the all of my searching and they told me they couldn’t. Can I ask, how were you able to run it?

    I renamed the root .htaccess file, leaving the one in the public_html directory, and had Bluehost help to remove the old version of PHP from the file. I also renamed the php.ini file.

    Thanks again, Mark! I think I’m back in working condition now. ♥

    • This reply was modified 5 years, 7 months ago by hhfarmstead.
    Anonymous User 3392934

    (@anonymized-3392934)

    Awesome, I’m glad to hear this got sorted out – I checked from our side, and your site is connected.

    I have been working with Bluehost to try to see if they would run the command that I found in the all of my searching and they told me they couldn’t. Can I ask, how were you able to run it?

    Just in case this should come up again, the command is:

    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://hilltophavenfarmstead.com/xmlrpc.php' && echo

    We’ll be here if you’d like help again – for now, I’ll mark this thread as resolved. 🙂

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

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