• Resolved gabrielangel

    (@gabrielangel)


    Hi,

    My Web Hosting block the default xmlrpc.php access.

    There are plenty of bots and brute force attacks to that file in particular.

    The solution is simply to rename the file and that was working pretty well with the latest versions of WordPress.com App and Jetpack as I could simply add the path to my renamed xmlrpc file.

    Now WordPress.com App is intergrated with Jetpack and I can’t access my blog directly and I can’t find a setting inside Jetpack to connect to my blogs.

    What can I do? is there a hidden setting or a workaround?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor James Huff

    (@macmanx)

    We do not currently have a way to set an alternative path, but when active, Jetpack will protect your xmlrpc.php file against brute force attacks.

    Unfortunately, blocking XML-RPC is not a great solution for fighting security risks. It’s akin to selling your car because you don’t want it to be stolen.

    Your site’s XML-RPC file is kind of like a communication gateway to your site. Jetpack, the WordPress Mobile Apps, and other plugins and services will use this file to communicate to your site. If this is blocked, you will have other issues pop-up down the road for the same reasons.

    I would suggest contacting your hosting provider and asking them to unblock your site’s XML-RPC. The most popular hosting providers out there have managed to find other ways to protect their servers without having to hinder your site and your ability to use services with your WordPress site.

    If using Cloudflare for the sites DNS then a site is protected so that Jetpack IPs can access XML-RPC but will block other requests.

    https://support.cloudflare.com/hc/en-us/articles/218377098-WordPress-Jetpack-and-Cloudflare

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘xmlrpc.php – rename file in Jetpack settings’ is closed to new replies.