This is available on Subscription Tiers: 

Engage, Grow, Promote, Free Unlimited, Essentials, Accelerate, & Ultimate.

When publishing Workouts from Wodify to your WordPress site, the XML-RPC connection between the two systems must be reachable and accept requests. These errors explain the usual causes and the steps you can take to resolve them so your Workouts publish reliably.

Pre-requisite Pro-Tip

Before troubleshooting, confirm two things: (1) you have an active WordPress site with an accessible xmlrpc.php endpoint, and (2) you have an Admin username/password for that WordPress site to use in Perform > Settings > Web Integration.

Pro-Tip: Security plugins (or your web host) commonly block external access to xmlrpc.php — temporarily disable Jetpack or any security/firewall plugins while testing, and if you host with a managed provider (e.g., GoDaddy), check their policies about XML-RPC access.

Step-By-Step How To Verify and Configure the XML-RPC Connection

1. In Wodify, go to Perform > Settings > Web Integration and confirm the URL you entered for your XML-RPC endpoint.

2. To find the correct XML-RPC URL: take your WP admin URL (https://your-site.com/wp-admin) and replace wp-admin with xmlrpc.php → https://your-site.com/xmlrpc.php.

3. Open that xmlrpc.php URL in your browser. A working endpoint typically returns a simple message (for example: “XML-RPC server accepts POST requests only.”) — if you see that, the file is present and publicly reachable.

4. If your WP admin uses redirects (www → non-www, http → https, or a plugin), use the final destination URL for xmlrpc.php in the Wodify config (test the final URL in a browser to confirm).

5. Once the URL looks correct, ensure the WordPress username/password in Perform > Settings is correct and has sufficient privileges. If your site requires additional security steps (2FA, application passwords, IP restrictions), address those before testing.

6. If the browser shows errors or blocks, try temporarily disabling Jetpack/security plugins and retry. If the site is hosted on shared or restricted hosting, contact your host to confirm external XML-RPC access is permitted.

Error messages, causes, and recommended fixes

ERROR: Method Not Allowed or Service Temporarily Not Available

Cause: Your web host or site is denying Wodify permission to post to xmlrpc.php (this is typically a server/host or plugin-level block).
Fixes:

• Disable Jetpack and any security/firewall plugins and retest.

• Contact your web host and ask whether external access to xmlrpc.php is blocked for your account (shared hosting sometimes blocks it). Ask them to allow external POST requests to xmlrpc.php.

• If the host shows a temporary service problem, ask them to investigate the server logs for denied POSTs from Wodify.

ERROR: Not Found

Cause: The xmlrpc.php URL entered into Wodify is incorrect, the xmlrpc.php file is missing, or the file is blocked from public access.
Fixes:

• Confirm the URL by replacing wp-admin with xmlrpc.php in your admin URL and test it in a browser.

• If the page shows a WordPress XML-RPC message then the file exists — use that exact URL in Wodify.

• If you see “Not Found,” confirm the file is present on the server and that there are no rewrite rules, redirects, or server rules hiding xmlrpc.php. Ask your host if the file is missing or intentionally blocked.

ERROR: Invalid Login

Cause: The username or password stored in Wodify is incorrect for the WordPress site.
Fixes:

• Double-check the username and password in Perform > Settings > Web Integration. The account should have appropriate privileges.

• If you cannot update credentials yourself (or you suspect the password was changed externally), contact support@wodify.com and our team can assist with backend updates.

ERROR: Banned

Cause: A host-specific block — commonly a GoDaddy message indicating the WordPress plugin or activity is blacklisted by the host.
Fixes:

• This is usually a hosting provider restriction. Check GoDaddy (or your host’s) documentation for the specific ban and contact their support to lift or explain the block.

• If the ban references a plugin, remove or replace the plugin or contact the host for remediation instructions.

ERROR: Unable to connect to the remote server — the connection was closed unexpectedly

Cause: Wodify did not receive the expected response from WordPress: the connection dropped, the server reset the connection, or something interrupted the network.
Fixes:

• If it happens only occasionally, it may be an intermittent network blip — retry.

• If recurring, verify xmlrpc.php loads in a browser and there are no middleboxes (firewalls, security plugins, or CDN rules) closing connections.

• If your site redirects, ensure Wodify is configured to use the final destination URL (no redirects).

• Work with your host to check server logs for closed or reset connections at the times of the errors.

ERROR: Request Timeout

Cause: The Wodify server did not get a timely response from your WordPress site — usually a sign of networking or server performance issues.
Fixes:

• If it was isolated, it may be transient. If persistent, check your server performance and any firewall or security rules that throttle or drop external requests.

• Confirm that xmlrpc.php opens quickly in a web browser from multiple networks.

• If xmlrpc.php is reachable but slow, work with your host to resolve latency or blocking issues.

ERROR: Server returned a fault exception: [-32700] parse error. not well formed

Cause: The Workout content includes characters that break the XML payload (common culprits: -, %, #, @, or other special characters when not escaped).
Fixes:

• Remove or replace special characters from the Workout content (title, description, or body), then click Publish Now to manually post.

• Avoid unescaped special characters in titles or rich text fields that will be sent via XML-RPC.

FAQs

How do I quickly test whether xmlrpc.php is reachable? Replace wp-admin with xmlrpc.php in your WordPress admin URL (e.g., https://your-site.com/xmlrpc.php) and open it in a browser. A healthy endpoint often returns a simple message such as “XML-RPC server accepts POST requests only.” If you get “Not Found” or server errors, the endpoint isn’t accessible.

Why does Jetpack cause publishing problems?Jetpack and some security plugins alter how XML-RPC requests are handled or add protections that block external POSTs. Temporarily disabling Jetpack (or the security plugin) while you test will show whether it’s the cause. If Jetpack is required, consult Jetpack docs for XML-RPC compatibility steps.

My host says my site is “banned” or blocking requests — what do I tell them? Explain that Wodify needs to post XML-RPC requests to xmlrpc.php and ask them to allow external POST requests to that file for your account. If they reference a plugin blacklist (GoDaddy does this), request guidance on how to remove the block or which hosting plan/settings allow XML-RPC access.

Which characters specifically cause the “not well formed” error? The error is caused by characters that aren’t properly escaped for XML in your Workout content (examples reported: -, %, #, @). Remove or replace such characters in the title/body and retry publishing.