Support » Plugin: Wordfence Security » Make XML-RPC publicly accessible?

  • Resolved LuciFit


    Hi, Just finished a new blog ( and set up JetPack to add sharing buttons to all pages. The FB button doesn’t work and when I looked it up, Jetpack says it’s a known issue that it doesn’t work with wordfence unless it’s configured to make XML-RPC publicly accessible.
    Can you please share with me how to do this? Or, maybe recommend a SM sharing widget that does work well with Wordfence. Thanks so much!

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Wordfence


    Hi Luci,

    Please let me know exactly what message you received from Jetpack telling you that something is incompatible with Wordfence. This is the first I’ve heard of this and I’d rather fix it than provide a workaround.



    Hi, Mark,
    I sent you an e-mail as well. Ran into this info because I was having problems getting Jetpack Social Sharing option to work with Facebook.

    On the Jetpack site in the known issues section – Here:

    It says the following:

    WordFence, Better WP Security, Login Security Solution

    These plugins block access to your site’s XML-RPC file. This file is used by Jetpack to connect to, and must be accessible at all times. You will consequently need to configure these plugins to make sure that your site’s XML-RPC is publicly accessible.

    Please let me know what you think.

    I am having the same issue. Jetpack Publicize won’t work. If you know a solution, could you post it here please?

    There is no option to allow accessibility to XML-RPC built into Wordfence.




    olsonsp4c – I am thinking about going to another plugin for publicity. I love the look of Jetpack, but the FB is the problem. It won’t grab the images. It works sometimes, but not always, and I’d rather keep Wordfence because I think they’re really helpful.



    +1 from me. I’ve really like Jetpack, but also need to use WordFence.

    Hey Mark… how about a response?

    @bgalbraith – If you need help, please start your own thread as per:

    The problem is that after reading about a dozen of these threads nobody is posting a solution. Maybe the moderators could help things along by prompting techs to actually state what the fix is then you wouldn’t have this problem. Just a thought.

    I’m sympathetic to your frustration, but moderators (nor anyone else) has any control over what plugin developers do or don’t do so far as support. Since this is marked resolved, it’s much less likely to get a reply from the developer than a new thread.

    BTW, did you read this?

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Make XML-RPC publicly accessible?’ is closed to new replies.