Jetpack stopped publishing to Twitter FB and Linked in

Also the first problem was that WordPress deactivated itself after I updated it last week… this seems to have caused the above problem.

I’d like to bump this. We, too, are having issues publishing to these specific platforms (Facebook, Twitter & LinkedIn) after the last update.

Checking our Sharing settings, all three of these services have been disconnected. Trying to reconnect results in the following Publicize error: -32300.

Our site has the correct OG data in every page. See these debugger results for and example reference: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fsneezingcow.com%2Fproduct%2Fscavengers%2F

Thoughts?

@davee: It is considered impolite to interrupt another poster’s ongoing thread unless you are posting a solution or suggestion. As per the Forum Welcome, please post your own topic.

@esmi,

I added additional debugging information to the original topic. They are related. I see this as helpful, not hurtful to the overall topic.

As a plugin developer, having multiple posts related to the same issue is more difficult to manage than one thread.

Getting a little picky here, eh? ??

@davee: These forums have guidelines. Please read them. As you will see, one of these guidelines – entitled Where to Post – specifically states:

Unless you are using the same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme & configurations as the original poster, do not post in someone else’s thread. Start your own topic.

Please abide by this.

@esmi,

Wow, seriously. I’m sorry. I’m aware of and understand the guidelines. However, my initial comment was only meant to be helpful, not hurtful.

The guidelines are specifically called “guidelines” and are only partially enforced and moderated. (See any “less busy” forum than the ones for Automattic-owned plugins & themes.)

Really, I am sorry and will post my own topic and or find help elsewhere. I mean no disrespect to you personally or professionally. I’m just hoping to get some help for my client and hope we’re all able to build sweet stuff with a sweet platform, together.

Thank you for the heads up.

Hi @belindajohnstone and @davee,

-32300 errors are different for each site in many cases. In short, something is preventing Jetpack’s server from accessing your site through the expected XMLRPC methods. Could be a different plugin, could be a misconfigured server, etc, so while related, @esmi is right on that these need separate issues per occurance.

That said, could you each please use Jetpack’s Debugger to send us some more information about your site?

To do so, follow these steps:

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 with a link to this thread and your name and email address.
5) Click the “Contact Support” button.

Thanks! I’m marking this as resolved and will help both in individual replies to the debug information.

Hi @brandonkraft, Thanks for your reply. It seems it’s probably ithemes security (formerly better wp security) as it says there is a problem with connection… unable to make XML-RPC request.
Can you suggest how to make it allowable?

Actually, in my setting the section ‘Disable XMLRPC’ is set as off, so it says it should function normally?

OK, I believe my issues are solved. In the update, Jetpack deactivated itself, and then that stuffed the connection to wordpress.com

Simply disconnecting and reconnecting made it all happen again.

Glad everything is resolved now. If you need anything else, let me know!