Title: Errors with Jetpack Publicize
Last modified: August 24, 2016

---

# Errors with Jetpack Publicize

 *  Resolved [319](https://wordpress.org/support/users/noyz319/)
 * (@noyz319)
 * [11 years ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/)
 * My site is ugsmag.com
 * A horrible cycle of badness just started today when I tried to connect a tumblr
   page and it connected to the wrong one (I have a few under the same login and
   it never asks you to choose which page you want to publicize to).
 * **#1.** I clicked the X to disconnect this wrong tumblr and as soon as I click“
   Ok” when prompted with ‘Are you sure you want to stop Publicizing posts to this
   connection?’ it takes me to an error page saying “**You do not have sufficient
   permissions to access this page.**“
 * **#2. **This action also somehow disconnects jetpack from wordpress.com and then
   when I click the button to try and re-connect to WordPress I get an error page
   saying:
 * **Invalid request, please go back and try again.
    Error Code: invalid_client 
   Error Message: The required “client_id” parameter is missing.
 * **#3.** At this stage, I have to deactivate + re-active jetpack and then it lets
   me connect and authorize.
 * **#4.** I can then configure all the different jetpack, activate and disconnect
   features, save changes etc… except when it comes to publicize. All of my social
   accounts are disconnected at this stage and if a click “connect” next to any 
   of them I blank white modal dialog box opens up and loads nothing (though If 
   i click the twitter connect i get to re-authorize that one before the white dialog
   box of death show up) then I’m back to error **#1** with the “You do not have
   sufficient permissions to access this page” error, then being disconnect from
   wordpress again, then doing all this over and over to to no avail.
 * I’ve tried deleting jetpack from the FTP and re-upping a freshly downloaded one,
   but I can’t break this error cycle with publicize. Please help!
 * [https://wordpress.org/plugins/jetpack/](https://wordpress.org/plugins/jetpack/)

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

 *  [Ryan C.](https://wordpress.org/support/users/ryanc413/)
 * (@ryanc413)
 * [11 years ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022630)
 * I’m sorry to hear about the trouble!
 * I’ve reset all of your Publicize settings on our end. Can you please follow these
   instructions to completely remove your old connections?
    [http://jetpack.me/support/publicize/facebook/#reconnecting-facebook](http://jetpack.me/support/publicize/facebook/#reconnecting-facebook)
   [http://jetpack.me/support/publicize/twitter/#reconnecting-twitter](http://jetpack.me/support/publicize/twitter/#reconnecting-twitter)
   [http://jetpack.me/support/publicize/linkedin/#reconnecting-linkedin](http://jetpack.me/support/publicize/linkedin/#reconnecting-linkedin)
   [http://jetpack.me/support/publicize/google/#reconnecting-google](http://jetpack.me/support/publicize/google/#reconnecting-google)
 * Then, try to connect them once again and see if the issue persists.
 * Please let me know how that works for you, and we can go from there!
 *  Thread Starter [319](https://wordpress.org/support/users/noyz319/)
 * (@noyz319)
 * [11 years ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022704)
 * Thanks! That fixed it.
 *  Thread Starter [319](https://wordpress.org/support/users/noyz319/)
 * (@noyz319)
 * [11 years ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022733)
 * Ughh. I tried to connect tumblr again this morning and am back to where I started
   with my initial post, all the same errors. Could you please reset it on your 
   end again? I’ll stay away from the tumblr connection.
 *  [Ryan C.](https://wordpress.org/support/users/ryanc413/)
 * (@ryanc413)
 * [11 years ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022772)
 * It looks like there’s an issue with Jetpack’s connection on your site now. Could
   you please try disconnecting and then reconnecting Jetpack to WordPress.com?
 * To do so, navigate to Dashboard > Jetpack. Then, scroll to the bottom of the 
   page and click the “Disconnect from WordPress.com” link. After doing so, click
   the “Connect to Get Started” button to reconnect.
 * Please let me know when you have done so, and I will check that your connection
   is working properly on our end. Then we can troubleshoot the Publicize issues
   if they persist.
 *  Thread Starter [319](https://wordpress.org/support/users/noyz319/)
 * (@noyz319)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022780)
 * Alright i’ve disconnected and re-reconnected wordpress.com to jetpack. Won’t 
   touch publicize yet, until you say it’s ok.
 * Each time publicize worked fine connecting to facebook, twitter, and google but
   both times it was trying to connect/disconnect from Tumblr that broke jetpack.
 *  [Ryan C.](https://wordpress.org/support/users/ryanc413/)
 * (@ryanc413)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022789)
 * Thanks for the update! Your connection looks good on our end now.
 * Could you try giving Publicize another try?
 *  Thread Starter [319](https://wordpress.org/support/users/noyz319/)
 * (@noyz319)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022790)
 * Broke again.
 * Clicked to connect to facebook and it gave me the same empty white modal window
   and disconnected me from wordpress.com … back the cycle where i’m getting the
   error:
 * Invalid request, please go back and try again.
    Error Code: invalid_client Error
   Message: The required “client_id” parameter is missing.
 * when i try and click “connect to wordpress.com” … just deactivated and re-activated
   Jetpack and i was able to connect / authorize, but still back to where I was 
   at the start of the problem.
 *  [Ryan C.](https://wordpress.org/support/users/ryanc413/)
 * (@ryanc413)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022791)
 * Can you please use Jetpack’s Debugger module to send us some more information
   about your site?
 * 1) Go to the Jetpack page in your dashboard.
    2) Click on “Help” tab in the upper
   right side of the page and click the link for “Jetpack Debugging Center.” 3) 
   Click the link that says “click here to contact Jetpack support.” 4) Fill in 
   the description box and your name and email address. 5) Click the “Contact Support”
   button.
 * Thanks!
 *  Thread Starter [319](https://wordpress.org/support/users/noyz319/)
 * (@noyz319)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022792)
 * Sent.
 *  [Ryan C.](https://wordpress.org/support/users/ryanc413/)
 * (@ryanc413)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022794)
 * Thank you! We’ll review those results, and then follow-up via email.

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

The topic ‘Errors with Jetpack Publicize’ 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/)

## Tags

 * [publicize](https://wordpress.org/support/topic-tag/publicize/)

 * 10 replies
 * 2 participants
 * Last reply from: [Ryan C.](https://wordpress.org/support/users/ryanc413/)
 * Last activity: [10 years, 12 months ago](https://wordpress.org/support/topic/errors-with-jetpack-publicize/#post-6022794)
 * Status: resolved