Jetpack invalid_client plugin re-activation error

Could you try to completely delete the plugin from the Plugins menu, and then reinstall from scratch?

Let me know how it goes.

I’m also seeing that on one of our sites. We’ve got a multi-site installation, so I’d rather not uninstall/reinstall.

I first noticed my own blog hosted on the server had a message that WordPress.com had different siteurl and home info than the site’s settings. Don’t know how that happened, as I’d had Jetpack connected for quite a while. I disconnected it and reconnected it without difficulty yesterday.

Today a student came in and was getting the same message at the top of her admin dashboard. What’s strange is that I use a custom domain on my blog, but she didn’t have that on her site. I disconnected and, when I tried to reconnect, that’s when I got the error buley copied above. I tried in Chrome and in Firefox and got the same error in both browsers.

Being a superadmin, I checked 6-8 other sites and didn’t see the discrepancy message on any other dashboard. I found one site that had not been connected before. I connected it to WordPress.com without problem. I haven’t tried disconnecting other sites, but am willing to do so.

@dcsolida could you try to delete the jetpack_options row in the wp_options table for that subsite, and see if it helps when they try to reconnect?

I reinstalled and zapped the options, seemingly to no avail. The clientid=1 param is generated on the WordPress side, which I didn’t notice before, so you’d think that uninstall/reinstall would work but I’m not yet seeing this to be the case. Trying again soon.

I ran into the same error message on one of my sites after Jetpack being installed & activated for quite a while (2 years+). After deactivating & reactivating everything seems to be working but I have some concerns about why this has happened in the first place.

Any feedback would be greatly appreciated.

why this has happened in the first place.

That’s something we’re looking into. You can follow our progress here:
https://github.com/Automattic/jetpack/issues/2218

Thank you Jeremy! If I can help in any way please let me know.

The 3.8.2 update just took 3 of my sites offline while trying to update through the built in wordpress updater. I deleted the /jetpack/ directory from all 3 and uploaded a fresh copy from www.ads-software.com . I also had to manually activate, then deactivate, and then reactivate the plugin after reuploading it in order to get jetpack to reconnect. Prior to doing all of this I had the same invalid_client message everyone else is mentioning.

Possibly related interaction: https://i.imgur.com/F5DATF9.gif

Does everyone have a Memcache backend or was that just me? That seemed like a possible correlating factor according to the Github issue.