A possible reason why Jetpack can’t connect to your WordPress

Do you you experience one of the following issues?

1. When you install or reinstall Jetpack, and want to connect to WordPress.com to get the stats module work, you see an alert:

Your website needs to be publicly accessible to use Jetpack: site_inaccessible

Error Details: The Jetpack server was unable to communicate with your site (HTTP 403). Ask your web host if they allow connections from WordPress.com. If you need further assistance, contact Jetpack Support: http://jetpack.me/support/

2. When you have Jetpack installed and connected to WordPress, and when you want to connect new profiles in Publicize module, you get an alert:

Something which should never happen, happened. Sorry about that. If you try again, maybe it will work.

Error code: -32301

The possible reason is that access to your xmlrpc.php file is limited. Somewhere in the past you may have done it yourself and forgot.

A year ago many WordPress bloggers were experiencing brute force attacks. The usual way to block access to wp-login, wp-admin, or xmlrpc files was to paste a relevant piece of code into htaccess file.

In case of xmlrpc.php this is something like that:

# BEGIN xmlrpc block
Files xmlrpc.php>
Order deny,allow
Deny from all
# Your IP address
Allow from
# END xmlrpc block

Anyone having Yoast’s SEO plugin can do that via Edit Files, so this was pretty easy to do. There is no reason to access WordPress installation via ftp.


You have to remove the xmlrpc-blocking condition, but just to let Jetpack connect relevant modules. Once it’s done you can put the blocking condition back.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com 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

%d bloggers like this: