Unable to communicate with your site

  • Resolved psychobreak

    (@psychobreak)


    8 years, 8 months ago

    Hi,

    Jetpack says

    site_inaccessible
    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.com/support/

    I asked my web host and they said you can add your .htaccess

    <FilesMatch “xmlrpc.php”>
    Allow from all
    </FilesMatch>

    Isn’t allowing for everyone risky? How can I allow just Jetpack?

    Thanks,

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter psychobreak

    (@psychobreak)

    I know it could change time to time but can you give the ip addresses?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Isn’t allowing for everyone risky?

    That shouldn’t be an issue. Most popular hosting providers do not block access to XML-RPC.

    To add an additional security level to your site, I’d recommend the following:

    1. Enable Jetpack’s Protect module. It will then protect your log in form as well as your XML-RPC file.
    2. Use a plugin like this one to disable XML-RPC Pingbacks, a common attack vector in WordPress:
      https://www.ads-software.com/plugins/disable-xml-rpc-pingback/
    3. Use a Website Application Firewall like CloudFlare or Sucuri: they will block attacks before they can even reach your site.

    I know it could change time to time but can you give the ip addresses?

    I would recommend against this approach, as our IP addresses will change over time, thus breaking your Jetpack connection.

    So if the actual issue the ability to use xmlrpc, the error message should be improved to say this. Popular security plugins block this, and it would be a mistake to contact the website host.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Unable to communicate with your site’ is closed to new replies.

Tags