How to enable XML-RPC

By default, Staq disables XML-RPC for security reasons. XML-RPC is a protocol that allows communication between WordPress and external applications, but it is also a common target for brute force and DDoS attacks. Therefore, unless it’s necessary for your website’s functionality, it’s generally safer to leave it disabled.

Why a Website Needs XML-RPC

XML-RPC is required for the following use cases:

• Publishing content remotely via mobile apps or external platforms.
• Communicating with certain third-party services, such as Jetpack or remote management tools like ManageWP.
• Enabling external applications to interact with your WordPress site, such as syncing or managing data.

Why It’s Better to Keep XML-RPC Disabled If Not Required

Although XML-RPC can be useful, it also opens up vulnerabilities, including:

• Exposure to brute force attacks since it allows remote login attempts.
• Potential for DDoS amplification attacks due to the ability to make repeated requests.
• Increased security risk by providing an additional entry point for attackers.

For these reasons, we recommend keeping XML-RPC disabled unless you absolutely need it.

Steps to Enable XML-RPC

To enable XML-RPC on your website, follow these steps:

• Log into the site’s Staq Panel.
• Click NGINX Config.
• Go to the Access Control subtab.
• Under Allow XML-RPC, select Yes from the dropdown menu.

By following these steps, XML-RPC will be enabled for your website. Be sure to monitor the site for any unusual activity if you enable this feature.