Title: Cannot Connect to Jetpack
Last modified: August 21, 2016

---

# Cannot Connect to Jetpack

 *  Resolved [infodabidjan](https://wordpress.org/support/users/infodabidjan/)
 * (@infodabidjan)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/cannot-connect-to-jetpack/)
 * Hello Jeremy,
 * I am not able to connect to publicize. I keep get following error message:
 * 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
   406]. Ask your web host if they allow connections from WordPress.com. If you 
   need further assistance, contact Jetpack Support: [http://jetpack.me/support/](http://jetpack.me/support/)
 * *************
    The hoster said that, it is not something from them and therefore
   cannot assist with that. Is there something you can assist with?
 * The site name is [http://www.infodabidjan.net](http://www.infodabidjan.net)
 * [https://wordpress.org/plugins/jetpack/](https://wordpress.org/plugins/jetpack/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Brandon Kraft](https://wordpress.org/support/users/kraftbj/)
 * (@kraftbj)
 * Code Wrangler
 * [12 years, 3 months ago](https://wordpress.org/support/topic/cannot-connect-to-jetpack/#post-4983698)
 * Hi,
 * I’m afraid your hosting company is incorrect. The HTTP 406 indicates the your
   server is returning the 406 status back to Jetpack during the connection process,
   likely due to a mod_security rule.
 * In some cases, simply trying again can get passed it depending on the rule being
   violated (for example, if the random token that is being used happens to contain
   something in violation of the rule).
 * Checking your site now, it looks like everything is okay now. If you need anything
   else, please let me know.
 * Cheers.
 *  [propelfolio](https://wordpress.org/support/users/propelfolio/)
 * (@propelfolio)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/cannot-connect-to-jetpack/#post-4983781)
 * Hi Brandon I have the same issue, other website in the same server is working,
   but one (www.propelfolio.com) it’s not. I disable all plugins and even set a 
   default theme from wordspress and still can’t connect.
    I always get The Jetpack
   server was unable to communicate with your site [HTTP 406].
 * Thanks
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [11 years, 11 months ago](https://wordpress.org/support/topic/cannot-connect-to-jetpack/#post-4983783)
 * [@propelfolio](https://wordpress.org/support/users/propelfolio/) Like infodabidjan
   above, you’ll want to contact your hosting provider and ask them to make sure
   they do not block connections to your site’s XML-RPC file via custom Mod_Security
   rules. That’s what’s causing the issue at the moment. Here is the error we get
   when trying to connect to your site from WordPress.com servers:
 * `<head><title>Not Acceptable!</title></head><body><h1>Not Acceptable!</h1><p>
   An appropriate representation of the requested resource could not be found on
   this server. This error was generated by Mod_Security.</p></body></html>`

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cannot Connect to Jetpack’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/cannot-connect-to-jetpack/#post-4983783)
 * Status: resolved