Plugin: Jetpack

  • Resolved WEB

    (@williamebales)


    8 years, 8 months ago

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

    Did a search in previous posts and asked my host provider if xmlrpc.php was blocked and they said no. I asked if the file was present in the subdomain that I was referring to and they said yes. Nothing was being blocked on the server.

    So now I’m requesting some help please.
    https://funding.starsofhollywoodnetwork.com/

Viewing 1 replies (of 1 total)
  • Thread Starter WEB

    (@williamebales)

    After reviewing the security settings, I found that by enabling the “Enable Pingback Protection” it blocks the Jetpack from accessing your website (site_inaccessible). If you are using WordPress Security measures then check to make sure that this is unchecked while trying to connect the Jetpack to WordPress.com for updates. Also another important note: If you have multiple domains or subdomains listed under the primary tree of your primary domain and you have this pingback protection on it will effect all subdomains as the master control even if you have the security package installed in the subdomain itself and unchecked.

    (Because your primary domain is checked for pingback protection, it will stop all outside pingbacks for all subdomains as well as the directory tree is underneath the protection of the primary domain. So if you are having this problem in a subdomain, check your primary settings on the primary domain as they do effect subdomains as well. Generally I’ve found that most reasons the XML-RPC may be blocked is due to this type of security setting issue or permissions.

Viewing 1 replies (of 1 total)
  • The topic ‘Plugin: Jetpack’ is closed to new replies.