Title: [Plugin: Jetpack by WordPress.com] Jetpack connect problem
Last modified: August 20, 2016

---

# [Plugin: Jetpack by WordPress.com] Jetpack connect problem

 *  Resolved [simpsonpw](https://wordpress.org/support/users/simpsonpw/)
 * (@simpsonpw)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/)
 * Jetpack connect problem. when I click “connect to wordpress.com” I am re-directed
   to my home page. What’s up with that?
 * [http://wordpress.org/extend/plugins/jetpack/](http://wordpress.org/extend/plugins/jetpack/)

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

 *  [Darcie](https://wordpress.org/support/users/darciemg/)
 * (@darciemg)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/#post-2519330)
 * I’m having the same issue. I click on “Connect to wordpress.com” with the url
   of [http://mydomain.com/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=xxxxxxxxxx](http://mydomain.com/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=xxxxxxxxxx),
   which redirects to [http://mydomain.com/register](http://mydomain.com/register),
   which redirects to my homepage as I’m already logged in. If I log out in another
   window and try it, I just get directed to register for my site.
 *  [Darcie](https://wordpress.org/support/users/darciemg/)
 * (@darciemg)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/#post-2519331)
 * Deactivating Buddypress allowed the Jetpack connection to go through. I’ll try
   reactivating it now that Jetpack connected. I know plugins aren’t written to 
   necessarily be compatible, but that’s a pretty popular one. I would suggest checking
   why the error occurs and remedying it, or posting the issue somewhere conspicuous.
   🙂
 *  [raywaldo](https://wordpress.org/support/users/raywaldo/)
 * (@raywaldo)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/#post-2519443)
 * In my case, it was a leftover in the MU-Plugins folder. Deleted that and Jetpack
   connected fine! [http://raywaldo.com](http://raywaldo.com)
 *  Plugin Contributor [Beau Lebens](https://wordpress.org/support/users/beaulebens/)
 * (@beaulebens)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/#post-2519444)
 * If you’re running BuddyPress, try 1. upgrading the latest version and/or 2. temporarily
   disabling BuddyPress. We’ve seen some incompatibilities that we’re working on
   fixing, but in the meantime this will allow you to connect at least.
 *  [rodtrent](https://wordpress.org/support/users/rodtrent/)
 * (@rodtrent)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/#post-2519445)
 * Yeah…experienced that here. BuddyPress is doing something to the xmlrpc file.
   In addition, to JetPack not being able to connect, it has also broken offline
   blogging clients that use the xmlrpc method to connect and post.

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

The topic ‘[Plugin: Jetpack by WordPress.com] Jetpack connect problem’ 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/)

 * 5 replies
 * 5 participants
 * Last reply from: [rodtrent](https://wordpress.org/support/users/rodtrent/)
 * Last activity: [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-jetpack-connect-problem/#post-2519445)
 * Status: resolved