not allowed to edit the jetpack_publicize_message

Hi there, @dream9studios,

Thanks for reporting this, and sorry for the trouble!

I suspect this could be an issue related to some plugins conflicting with Jetpack, but I cannot be sure about that as the Jetpack connection isn’t working at the moment, so I can’t investigate further on this.

As a first step to keep troubleshooting it, we need to reconnect Jetpack by fixing the block I can see at my end, which is happening at your server’s side.

Can you reach out to your host and ask them if they have any blocks or limits on your XML-RPC.php file??

It’s also worth checking whether any Jetpack IP addresses are blocked. The full IP range can be found at the bottom of this page:

https://jetpack.com/support/hosting-faq/

Also, check for any security/caching plugin you may have enabled, and try temporarily disabling them, to see if it fixes the problem. You may also want to search for any firewall on your server-side that might be blocking the communication with the xmlrpc.php file – your host should be able to help you with that.

Once done that, you can temporarily deactivate all your plugins and check if the problem gets fixed that way. If it works, then reactivate each plugin one by one to find out which one is causing problems.

Hope that’s all clear! Let me know how you get on, and we’ll take it from there if necessary.

I have just sent a message to my host about the XML-RPC.php. They should be getting back to me very soon. I’ll let you know what they say.

I already tried disabling all plugins and clearing my security plugin settings. No such luck.

Thanks for the fast update, @dream9studios

Let us know when the block is fixed and you reconnect Jetpack, so we can a closer look at it ??

My host says there are no blocks or limits on the XML-RPC.php so now I’m at a loss as to what could be causing any of these problems. :/

Hi @dream9studios

When we try to ping the xmlrpc.phop file, we’re seeing the following error:

The server has responded with a 429 response code, indicating explicit rate limiting.
The user will need to speak with their host to ensure that Jetpack or the mobile app in
question has unlimited access to XMLRPC. The host may need to allowlist our IP range,
which can be found at https://jetpack.com/support/hosting-faq/.

If it isn’t your host, do you have a Firewall plugin installed? You might need to add the IP range in that link to the Firewall to let Jetpack connect properly.

When I check the php link that my host gave me it says “XML-RPC server accepts POST requests only.” Is that right or should it say something else?

Hi there,

I checked your site and now it is showing the ideal message and the Jetpack connection is looking good too. Could you please check again if the publicize started working properly?

I’m sorry for the late reply, I’ve been having ISP issues all day.

I’m still getting this error message when I make a post: “Publishing failed. Sorry, you are not allowed to edit the jetpack_publicize_message custom field.”

Okay, I did an experiment. I setup a new WordPress installation in a subfolder on my main domain. I installed all the same plugins as my main installation starting with Jetpack and connected all the Publicize links. I created a post and… It worked! No errors at all.

I just can’t figure out why it will work on a fresh installation but not my other three older installations. I thought it might be my Litespeed Cache plugin but I tried disabling that and no luck. I’m at a complete loss unless it could be some sort of database error.

Hi @dream9studios

I’d suggest reinstalling Jetpack and reconnecting it according to the steps in our guide:

https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack

You can then proceed to try editing the custom Publicize message; however, be sure to do this on your WP-Admin account that has the full Administrator role and permissions.

If the issue persists after that point, please do reach out to us here so we can investigate this further after getting access.

Don’t forget to include a link to this thread if you go ahead with that!

• This reply was modified 2 years, 7 months ago by Mehdi Benchalal.

I found out that I got this error when I tried to assign a Stick to the Top checkmark to a new post when there was already a post with a to the top Sticky. After I removed it from the new post, the post went through. Then I removed it from the old post and was able to make the new post sticky.

UPDATE: well it worked one time but the error returned.