XMLRPC Error on GoDaddy Hosted Blogs

Over the past 24 hours we have heard from various WordPress bloggers who use GoDaddy as their web host, who have been experiencing issues connecting to their blogs. BlogPad Pro (and all other mobile apps) use the inbuilt XMLRPC file to communicate with your WordPress blog, but GoDaddy users are getting an error message saying:

“Failed whilst testing XMLRPC service…”


Why am I getting this error?

From what we can tell, it seems that GoDaddy have added some kind of Firewall rule that prohibits proper use of the XMLRPC API (Application Programming Interface – the means by which all mobile apps communicate with your blog). We haven’t confirmed this though as we are not able to contact GoDaddy about this directly.

What can I do to fix this?

First of all you’ll need to contact support at GoDaddy to let them know that they have broken some functionality on your blog by disabling XMLRPC access in this way.

In the meantime, we have found a way to get around the issue – by renaming the “xmlrpc.php” file found in the root folder of your blog. We recommend that it is renamed something that does not include “xmlrpc” in the name, so something like “bpp-api.php” should be fine.

Now, if you’re adding your blog for the first time to BlogPad Pro, then in the “URL” field simply add the full URL path to the newly named file, eg:


If however you wish to do this for a blog that has already been added to BlogPad Pro, you can update the XMLRPC URL for the blog by doing the following:

  1. Go to “Manage Blogs” (ie tapping on the “B” button)
  2. Tap on the right-facing blue arrow for the blog in question to display the “Blog Options” menu
  3. From the “Blog Options” menu, tap on the “Edit Blog Settings”
  4. On the “Local Blog Settings” screen, edit the “XMLRPC URL” to be the newly renamed file
  5. Tap on “Save Changes” to save

If everything has worked correctly (i.e. BlogPad Pro can find your renamed XMLRPC file), then everything should be OK. If you encounter issues still, then please let us know.

Apologies for any inconvenience this may have caused, but this has been completely out of our control.

Let us know what you think

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s