blocked request 403

  • Resolved wordjunky

    (@wordjunky)


    2 weeks, 4 days ago

    I received the following error message from JetPack. My host is WPEngine and I have reset everything on that side. Also, I am not getting errors when I access the site via a browser.

    What is going on and how can I get rid of the error message? Other than deleting Jetpack, I’d rather not do that.

    ————————————— message ————————————

    A healthy Jetpack Connection allows connected plugins (such as Jetpack and WooCommerce) to provide features like Stats, Site Security, and Payments.

    Error WordPress.com reached your site but the request was blocked (HTTP 403). This is usually caused by a firewall, security plugin, or server rule rejecting requests from WordPress.com.

    Ask your host or security provider to allow requests from WordPress.com to your site’s xmlrpc.php file. Reconnecting will not resolve this. If you need further help, contact Jetpack support.

    • This topic was modified 2 weeks, 4 days ago by wordjunky. Reason: indicat the message I received

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Chatoxz (a11n)

    (@chatoxz)

    2 weeks, 2 days ago

    Hi there,

    Sebastian here, I hope you are doing well.

    Thanks for sharing that error message. I had a look at your site’s connection and can confirm what you described: something on WPEngine’s side (a firewall rule or security setting) is blocking WordPress.com‘s requests to the XML-RPC.php file and returning a “403 Forbidden” error. You can confirm that here: https://www.tnalpha.com/xmlrpc.php?for=jetpack. Even though the site loads fine in a browser and you have already reset things on the hosting side.

    In order to fix the issue, I would recommend asking WPEngine (or checking any active security plugin, like Wordfence or Sucuri) to allowlist WordPress.com and Jetpack’s IP ranges so these requests are not blocked going forward: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

    Let us know if you still see connection errors after that and we will dig further.

    Warm regards,

    wpdesignuser

    (@wpdesignuser)

    2 weeks ago

    Hi! Same problem here.

    I have Jetpack installed on several sites hosted on the same server, but I’m only getting this message on two of them.

    I have the BulletProof Security plugin installed on all of these sites. Apparently, it’s the plugin that is blocking it, but I’m not sure why this is happening only on some sites and not the others.

    Any ideas on what could be causing this?

    Thank you very much!

    Thread Starter wordjunky

    (@wordjunky)

    2 weeks ago

    I had both Jetpack and Wordsense plugins loaded on my site. When I turned Jetpack off the issue went away and the site began painting quicker. For now, I have dropped Jetpack and only use Wordsense. It’s a heavy handed way, but I was not using many options from Jetpack so no great loss.

    Ed Alexander

    (@edaitpro)

    2 weeks ago

    I checked the error message on the OP’s website and it’s generic error message: “You don’t have permission to access this file.” BPS displays a custom 403 error page if BPS is causing the 403 error.

    @wpdesignuser – BPS does not block XML-RPC by default. If you have added this additional Bonus Custom code in this link then remove it from BPS Custom Code > https://forum.ait-pro.com/forums/topic/wordpress-xml-rpc-ddos-protection-protect-xmlrpc-php-block-xmlrpc-php-forbid-xmlrpc-php/

    The BPS Security Log logs all 403 errors whether or not BPS is causing the 403 error. So check your BPS Security Log for clues to what is blocking the xml-rpc.php file.

    wpdesignuser

    (@wpdesignuser)

    1 week, 6 days ago

    Hi @edaitpro and thank you for your answer.

    Indeed, I did have the custom code enabled. I removed it, and apparently the message is no longer appearing.

    Thank you very much!

    Plugin Support fujifika (a11n)

    (@fujifika)

    1 week, 6 days ago

    Thanks for jumping in here, @edaitpro , much appreciated.

    Since both issues here look resolved, I’ll go ahead and mark this thread as solved. Feel free to open a new thread if anything else comes up!

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

You must be logged in to reply to this topic.