• I just updated my site to WP 3.6 as well as update Jet Pack to the current version. I went to connect to WordPress.com to activate it and got the error: 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: https://jetpack.me/support/

    https://www.ads-software.com/plugins/jetpack/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Could you post your site URL here, so I can have a look?

    If you want it to remain private, you can also contact us via this contact form:
    https://jetpack.me/contact-support/

    Thread Starter createwithjoy

    (@createwithjoy)

    create-with-joy.com

    Thread Starter createwithjoy

    (@createwithjoy)

    Here are a couple of other quick notes. I am on a shared Linus server with Hostgator. Also, there seemed to be a similar problem that required to “change the PHP_FCGI_CHILDREN to 2”. Because I am on a shared server, this is not possible.

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Jetpack communicates with your site using the xmlrpc.php file. If I go to this file on your site, I get a “Not Authorized” message:

    https://create-with-joy.com/xmlrpc.php

    So something on your site or your server is blocking access to this file. Jetpack will never function properly unless this file is accessible. Are you using a security plugin that might be blocking access? If not, can you ask your host if they are blocking access at the server-level?

    Thread Starter createwithjoy

    (@createwithjoy)

    Thanks for the help. My hosting coming was blocking xmlrpc.php. It was blocking this file because of mistaken attempt to improve load time.

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Great, let me know if you’re not able to connect to WordPress.com (your site isn’t currently connected).

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘site_inaccessible’ is closed to new replies.