Troubleshooting Errors when using WordPress with RightBlogger

Last Updated February 14, 2026

Having trouble connecting your WordPress site to RightBlogger? Don’t worry, we’ve got you covered! This guide covers the most common connection problems and how to fix them when using the WordPress integration.

Important Note: RightBlogger integrates with self-hosted WordPress sites (WordPress.org), not sites hosted on WordPress.com. WordPress.com doesn’t allow the necessary connections.

If you’re seeing an error that’s not listed below, please contact us any time, we’re happy to help!

Common Errors and Solutions

Here are some of the most frequent errors you might encounter with the WordPress integration, along with their causes and solutions:

Incorrect Username or Application Password

Sorry, you are not allowed to create posts as this user. - This is likely due to an incorrect username or application password.

What it usually means: There’s a problem with your username, email, or application password.

Possible Solutions:

Double-Check Your Credentials: Make absolutely sure you’ve entered your WordPress URL, username/email, and application password correctly. Typos happen!
Try Your Email Address: Instead of your username, try using the email address associated with your WordPress account.
Flush Permalinks: Go to your WordPress dashboard, navigate to Settings > Permalinks, and click “Save Changes” (you don’t need to actually change anything). This “flushes” the permalinks and can resolve some connection issues.
Check for Conflicting Plugins: Some plugins can interfere with WordPress’s built-in API. Temporarily deactivate any security or API-related plugins to see if that resolves the issue. (See “Known Plugin Conflicts” section below). We talk about this later in the guide.

You’ll also want to make sure your domain name matches your integration’s URL exactly. For example, if your site is “www.sitename.com”, it needs to include the “www.”

Fetch Failed (Not Found)

What it usually means: You’ve likely entered your WordPress site URL incorrectly.

Solutions:

Verify Your Homepage URL: Double-check that you’ve entered your site’s homepage URL correctly in your RightBlogger project settings. For example, if your site is example.com, enter example.com. Don’t enter your WordPress login page URL.
Subdirectory Installs: If WordPress is installed in a subdirectory (e.g., example.com/blog), make sure to include the subdirectory in the URL (example.com/blog).
HTTPS vs. HTTP: Ensure you’re using the correct protocol (https:// if your site has an SSL certificate, http:// if it doesn’t – but most sites should be using HTTPS these days).

Incorrect Password

"Error: The password you entered for the username example is incorrect. Lost your password?"

If you’re seeing an error saying your password is wrong but you know your username and application password are incorrect it could be one of two things.

EasyWP Hosting: If you’re using EasyWP, you must install the “Application Passwords” plugin. For some reason, EasyWP disables the built-in WordPress API authentication, and this plugin is required to fix it.
Conflicting Plugins: Certain plugins that modify API authentication can cause conflicts. Deactivate any plugins that might be interfering with the WordPress API. Try reconnecting after deactivating each plugin to identify the culprit (You might have a plugin called something like “JSON API”.)

Application Passwords Disabled by Wordfence

Wordfence disabling appliction passwords

he Wordfence security plugin, if installed, often disables WordPress Application Passwords by default.

Solution:

Go to Wordfence Settings: In your WordPress dashboard, navigate to Wordfence > All Options.
Find the Setting: Look for an option like “Disable WordPress application passwords” (the exact wording may vary slightly depending on the Wordfence version).
Disable the Setting: Make sure this option is unchecked (disabled) to allow Application Passwords to function.
Try to connect again.

The REST API has been restricted to authenticated users.

You have a plugin like Adminify that is preventing the JSON API on your WordPress site from functioning. This prevents RightBlogger from updating and sending content to your site. Uncheck “Disable REST API” in the security tab of Adminify. It also may be under “Admin and Site Enhancements ASE” plugin.

Sorry, you do not have permission to make REST API requests.

If you see an error saying you don’t have permission to make REST requests, a plugin like Perfmatters is likely blocking access to the WordPress API and preventing our plugin from working. Make sure any plugin that restricts the REST API has the option disabled.

Also in the Solid Security plugin this is under “API Access” in the “REST API” setting.

Please be sure JavaScript and Cookies are enabled in your browser and try again.

If you are seeing an error similar to “Sorry, there was an error. Please be sure JavaScript and Cookies are enabled in your browser and try again.” Your server likely is using a firewall like Cloudflare or WP-SpamShield.

Our user agent is RightBlogger/1.0 (https://rightblogger.com) if you’d like to allowlist our user agent.

Known Plugin Conflicts

These plugins are known to sometimes cause issues with WordPress API authentication. We have seen WordPress say that an application password is incorrect even though it’s not when they are active. If you have them installed, try temporarily deactivating them to see if it resolves the connection problem:

Basic API Authentication plugin (This is an outdated plugin and generally shouldn’t be used.)
JSON Basic Authentication plugin (Also outdated in most cases.)

Important Note: Always back up your website before making any significant changes, including deactivating plugins.

If you’ve tried all these steps and are still having trouble connecting, please don’t hesitate to contact us at [email protected]. We’re here to help!

Does RightBlogger work with WordPress.com sites?

RightBlogger works with self hosted WordPress sites (WordPress.org), not WordPress.com.

WordPress.com often blocks the kind of REST API access and authentication that RightBlogger needs to send drafts and publish posts.

If you are not sure which one you have, check your hosting. If you log into a web host like Bluehost, SiteGround, or WP Engine, you are usually on WordPress.org.

For setup steps and requirements, follow the guide in the WordPress Integration setup.

Why am I getting “Fetch Failed (Not Found)” when I try to connect WordPress to RightBlogger?

This usually means the WordPress site URL in RightBlogger is not the correct homepage URL.

In your RightBlogger project settings, enter your site home address like https://example.com. Do not paste the WordPress login page or an admin URL.

If WordPress is installed in a folder, include it like https://example.com/blog. Also confirm you are using the right protocol, which is usually HTTPS.

Once the URL is correct, reconnect and try again. If you still have trouble, recheck the same URL in your browser to make sure it loads.

RightBlogger says “Sorry, you are not allowed to create posts as this user.” How do I fix it?

This error usually points to the wrong username or application password, or a mismatch in your site URL.

First, double check your WordPress URL, username or email, and application password for typos. Many users fix it by switching from username to the email address on the WordPress account.

Next, flush permalinks in WordPress by going to Settings > Permalinks and clicking “Save Changes.” This can fix some hidden routing issues that affect the REST API.

If it still fails, temporarily disable security or API related plugins and try again. Some plugins can break authentication even when your credentials are correct.

My application password is correct, but WordPress says the password is incorrect. What should I do?

If the password looks correct but WordPress rejects it, a host or plugin is often blocking application password login.

If you use EasyWP hosting, you may need to install the “Application Passwords” plugin because EasyWP can disable built in API authentication.

Next, look for plugins that change API authentication, such as “JSON API” style plugins. Turn them off one at a time, reconnect, and see which one causes the issue.

Once the connection is stable, you can keep using RightBlogger to draft and publish posts without repeating the manual login steps each time.

How do I fix REST API errors like “restricted to authenticated users” or “no permission to make REST API requests”?

These errors almost always mean a plugin or security setting is blocking the WordPress REST API.

Plugins like Adminify or ASE can disable the REST API. In Adminify, uncheck the option like “Disable REST API” in its security settings.

Performance and security plugins can also block REST requests. For example, Perfmatters can restrict REST API access, and Solid Security has REST API controls under API Access.

After you allow REST API access, reconnect in RightBlogger and try sending a post again. For more context on supported CMS connections, see RightBlogger CMS Integrations.