Common Problems with WordPress – Zapier

## Error: Expat or Parsing

This type of error can have different causes:

*   If you just installed a plugin, it might be preventing Zapier from authenticating. Disable the plugin and try again.
*   The type of permalink used on the WordPress installation is causing trouble. To change the permalink type:
    *   In your WordPress site, go to **Settings**, then click **Permalinks**.
    *   Click any permalink option other than "Plain" (this is the default option).
    *   Click "Save Changes".

## Author is the Authenticated User Rather Than Specified Author

This can happen if the authenticated user does not have an appropriate role. Please review WordPress' details on [Roles and Capabilities](https://codex.wordpress.org/Roles_and_Capabilities) as you will need an authenticated user who at least has an Editor role to post as other authors.

## Error: 500 Internal Server Error or other trouble connecting

In order to connect to WordPress, you must have XML-RPC functionality turned on. This is turned on by default in WordPress 3.5+. If you're having issues connecting, go to Settings > Writing > Remote Publishing and check the checkbox.

You may also receive this error if your WordPress installation is secured and not publicly available. Unfortunately, the installation must be publicly accessible to work with Zapier.

Also, we're unable to provide IPs to allowlist as our IPs are not static - they rotate because we use AWS. If you'd like, you should be able to allowlist a block of IPs from AWS to make this work. You would just need to make sure the list you're allowing is the us-east-1 IP range.

AWS provides a list of their IP address ranges at [https://ip-ranges.amazonaws.com/ip-ranges.json](https://ip-ranges.amazonaws.com/ip-ranges.json). You can read more about how to use those IPs [here](https://zapier.com/help/firewalls-and-ip-restrictions/#how-do-these-ips-translate-into-ranges).

Additionally, Zapier's calls will always include the header `User-Agent: Zapier`, so this may be an alternative when allowing a whole range of IPs isn't feasible.

## Error: (403) Forbidden

Jetpack Protect (official WordPress module) will occasionally block some AWS IPs you can either allowlist the IP listed in the error, disable Protect altogether, or if try and allowlist all [AWS us-east-1 IPs](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html). You can read more about how to use those IPs [here](https://zapier.com/help/firewalls-and-ip-restrictions/#how-do-these-ips-translate-into-ranges).

*   **Allowlist with Jetpack** : [https://jetpack.com/support/security-features/#unblock](https://jetpack.com/support/security-features/#unblock).
*   **Allowlist the xmlrpc.php file**: You can find [help here](https://wordpress.org/support/topic/allow-xmlrpcphp/). You'll want to allowlist our AWS range (all the US-East IPs from [here](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)).
*   **Enable/Disable** : [https://jetpack.com/support/security-features/#enable](https://jetpack.com/support/security-features/#enable)

Once you do that, try [reconnecting your WordPress account](https://zapier.com/app/settings/authorizations) to see if this resolves the issue.

If you have a firewall enabled please double-check that it allows Zapier to connect as well.

## Error: XML-RPC server accepts POST requests only

This error could mean that you're using the wrong Base URL in the login screen. If you're using `http:` try using `https:`. If you're using `www.example.com` try using it `example.com`.

If you continue to get this error, then it's likely because the XML-RPC is being blocked on the WordPress site. It's most likely being blocked by a plugin, the hosting provider, or a security setting. To fix, try disabling a your plugins one and a time, then try reconnecting to WordPress account to see if you can isolate the problem plugin.

If not, it might be a back-end change that needs to be made by your hosting provider or website developer. We recommend reaching out to them and asking them to update the XML-RPC settings for you. You can send them this link for more information: [https://codex.wordpress.org/XML-RPC\_Support](https://codex.wordpress.org/XML-RPC_Support)

If your provider/developer wants to allowlist access to us, you can let them know that we use Amazon's AWS products for our server infrastructure, so they'll need to allowlist their IP list from the us-east-1 region. You can find that range list here: [https://ip-ranges.amazonaws.com/ip-ranges.json](https://ip-ranges.amazonaws.com/ip-ranges.json) . You can read more about how to use those IPs [here](https://zapier.com/help/firewalls-and-ip-restrictions/#how-do-these-ips-translate-into-ranges).

## Add a Custom Featured Image to your WordPress Post

In order to take an image from a previous step (like your Trigger, for example) and add it as a featured image on your post, you have to use 2 WordPress steps.

First, you use the 'Upload Media' step to add the image to your WordPress website:

![](https://cdn.zapier.com/storage/photos/aaa36d76a6738401dcaa59319231de8e.png)

Then, on your 'Create Post' step you make use of the image you just uploaded, by selecting "Use a Custom Value" for the 'Featured Media' field and then using the "Attachment ID":

![](https://cdn.zapier.com/storage/photos/f53026f8436425d3c85b37463e2e223d.png)

## Error: 401 Incorrect Password 

This may be due to using your Wordpress user login instead of your site login.

To fix this:

1.  Log into [Wordpress Classic Editor](https://wordpress.com/support/classic-editor-guide/):).
2.  Either:
    1.  Set a new password.
    2.  Create an application password for Zapier.

Use this password to connect your account in Zapier.