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 contact@rightblogger.com. We’re here to help!

Why won’t RightBlogger connect to my WordPress site?

This usually happens because the WordPress URL, username, or application password is not an exact match.

First, confirm you are using a self hosted WordPress.org site, not WordPress.com. WordPress.com blocks the type of connection RightBlogger needs.

Next, double check your site URL. Make sure it matches your real homepage, including www if your site uses it, and include a subfolder like /blog if WordPress is installed there.

If you still cannot connect, go to Settings > Permalinks in WordPress and click Save Changes. For step by step setup, follow the WordPress setup guide for RightBlogger.

I see “Fetch Failed (Not Found)”. What does that mean and how do I fix it?

“Fetch Failed (Not Found)” almost always means the website URL in your RightBlogger settings is incorrect.

Use your site’s homepage URL, like https://example.com, not your WordPress login URL. If your WordPress lives in a folder, use https://example.com/blog.

Also check HTTP vs HTTPS. Most sites should use HTTPS, and a mismatch can cause the request to fail.

Once your URL is correct, reconnect in RightBlogger and try again. This is one of the fastest fixes and it prevents publishing errors later.

WordPress says my password is wrong, but my application password is correct. Why?

This can happen when your hosting or a plugin blocks WordPress REST API authentication, even when your application password is correct.

If you use EasyWP hosting, install the Application Passwords plugin. EasyWP sometimes disables the built in authentication that RightBlogger needs.

Also check for plugins that change API login behavior, like older “JSON API” or “Basic Authentication” plugins. Temporarily deactivate them one at a time, then try connecting again.

After you find the conflict, you can usually keep everything working by leaving the REST API and application passwords enabled for your site.

How do I fix Wordfence blocking WordPress application passwords?

If Wordfence is installed, it often disables WordPress application passwords by default. That will stop RightBlogger from signing in and creating or updating posts.

In WordPress, go to Wordfence > All Options. Find the setting that says something like “Disable WordPress application passwords” and make sure it is unchecked.

Save your settings, then try connecting to RightBlogger again. If it works, you can keep Wordfence active and still publish through RightBlogger.

This is a common fix because Wordfence is popular and the setting is easy to miss.

What does “The REST API has been restricted” or “Sorry, you do not have permission to make REST API requests” mean?

These messages mean a security or performance plugin is blocking WordPress’s REST API. RightBlogger uses the REST API to send posts and updates to your site.

Check plugins like Adminify, ASE (Admin and Site Enhancements), Perfmatters, or Solid Security. Look for a setting like “Disable REST API” or “REST API Access” and turn that restriction off.

After changing the setting, reconnect in RightBlogger and test again. Keeping the REST API available helps your WordPress publishing workflow stay smooth and reliable.

If you want to confirm you are using the right integration approach, review the CMS integrations supported by RightBlogger.

How can RightBlogger help me publish to WordPress faster once the connection works?

Once your WordPress connection is working, RightBlogger can speed up writing and publishing by keeping your drafting and posting in one workflow.

You can write posts with the RightBlogger AI Article Writer and send them straight to WordPress without copy and paste. This saves time and reduces formatting mistakes.

You can also plan ahead by using RightBlogger scheduling, so posts go live when you want, even if you are not at your computer. See how to schedule posts with RightBlogger.

If you run into connection issues again, checking URL accuracy, application passwords, and REST API settings will solve most problems quickly.