I came here looking for an answer to the same question. I set up my Publicize to Facebook link a while back, and it seems to be working. Tonight I tried to connect my Twitter account and I keep getting the Error code: -32300.
I’d love to know how to fix this!
I’m having the same problem. Really frustrating.
So… no ideas on this? I’m surprised that people are having problems and this isn’t getting a response days later as it’s an official plugin. It’s genuinely an issue when you can’t actually share things you’re posting.
Hi,
I have the same problem.
is there a solution?
Hi all,
There are several reasons why someone may get this error. To troubleshoot it, please provide your URL, and for everyone but bowendesign, please.start a new thread, as per the Forum Welcome?
http://wordpress.org/support/plugin/jetpack#postform
Thank you!
Hi
My website is http://www.lyontownresto.fr
I installed a sharing button facebook without plugin, is what is it that could block?
I also Cloudflare on my site, is that you think that there is a mismatch between the DNS of Cloudflare or Jetpack?
Thank you
Heyho,
Sorry to get back to this so late. I solved my issue by uninstalling all the plugins, deleting the non-essential ones that might clash with Jetpack, and reinstalling them one-by-one. Unfortunately due to the method I used I couldn’t figure out which one it was doing it.
As a note, the commonly-attributed xmlprc.prp (or whatever file it was) security error, where it’s not writeable because of its permissions, wasn’t the root of the problem. So clearly there’s some issues between Publicise and a few of the similar plugins.
Not sure if that helps, but that’s how I solved it.
B
yes publicize_error=-32300
bug?
The fix is simpler than it sounds. Apparently an update changed a file permissions so you need to change a file permissions for one file. Easy to do via FTP.
See http://www.rackmire.co.uk/blog/guides/publicize-error-32300-jetpack-plugin-connecting-social-accounts/#comment-66 for details.
I had found the xlmrpc.php restricted WordPress’ ability to use that file. A simple permissions change was all I needed. Thanks to the website above. No need to test each app or whatever as some sites noted.
Leo
(@leowebdev)
worked fine. tks bro!
# Rules to disable XML-RPC
# <files xmlrpc.php>
# Order allow,deny
# Deny from all
# </files>
I had the same problem. I figured it out for our site. We use the plugin iThemes Security. We had the setting XMLRPC completely disabled by our webserver. I turned this off and everything worked just fine.
