Troubleshooting Errors When Using WordPress with RightBlogger
Find fixes for login and API errors, plus the Cloudflare rule that can unblock failed publishing without exposing your REST API.
Having trouble connecting your WordPress site to RightBlogger? This guide covers the most common connection problems with the WordPress integration and how to fix each one.
Important Note: RightBlogger works with self-hosted WordPress sites (WordPress.org) and may work with WordPress.com sites on a plugin-enabled paid plan. Free WordPress.com sites cannot install the RightBlogger plugin.
If you see an error that isn’t listed below, contact us.
Two ways to connect: You can connect WordPress to RightBlogger using either the RightBlogger WordPress plugin (get it on WordPress.org) or your WordPress username and an application password. Most of the errors below apply to application-password connections. If you are using the plugin and publishing fails with a 403 error, skip ahead to Cloudflare or a firewall is blocking RightBlogger, which is the most common cause.
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: Check that your WordPress URL, username or email, and application password are entered exactly. A single typo breaks the connection.
- 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.”
Could Not Resolve Your Site (Fetch Failed)

The error reads “We could not resolve your site (ENOTFOUND)” or “(EAI_AGAIN)”. Older versions just said “fetch failed”.
What it usually means: You’ve likely entered your WordPress site URL incorrectly, or the domain no longer points at your WordPress install.
Solutions:
- Verify Your Homepage URL: Double-check the site URL saved on your project’s WordPress integration (the project’s Integrations tab). It should be your site’s homepage URL. For example, if your site is
example.com, enterexample.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 correct, it could be one of two things.
- EasyWP Hosting: EasyWP disables the built-in WordPress API authentication that application passwords rely on. Connect with the RightBlogger plugin instead, since it does not use application passwords. The old Application Passwords plugin was closed on WordPress.org in December 2025, so don’t install 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

The 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. With the RightBlogger plugin, the same problem shows up as “Your site only lets logged-in users use the WordPress REST API, so it turned the post away.” Turn that option off, or allow /wp-json/rightblogger/ through it.
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.
Cloudflare or a Firewall Is Blocking RightBlogger (403 Errors)
If publishing fails with a 403 error, or you see a message like “Sorry, there was an error. Please be sure JavaScript and Cookies are enabled in your browser and try again,” your site is most likely running a firewall such as Cloudflare or WP-SpamShield that blocks RightBlogger’s requests to your WordPress REST API before they reach your site.
RightBlogger is a Cloudflare verified bot. Requests from the RightBlogger plugin are signed with Web Bot Auth, so Cloudflare can tell them apart from impostors and its bot protection lets them through. If you use the plugin and still get a 403, a custom rule or another security plugin is the likely cause, and the steps below allow RightBlogger past it.

RightBlogger’s requests identify themselves with:
- User agent:
RightBlogger/1.0 (https://rightblogger.com) - Plugin path:
/wp-json/rightblogger/v1/
To fix this in Cloudflare:
- In the Cloudflare dashboard, select your domain and create a new Custom rule. In the current dashboard this is under
Security > Security rules. - Add two conditions joined with AND: User Agent contains
RightBlogger/1.0, and URI Path starts with/wp-json/rightblogger/v1/. If you still use the legacy application-password connection, use the specific/wp-json/wp/v2/endpoint it calls instead of opening the entire REST API. - Set the action to Skip, then turn on the components to skip, at minimum All managed rules, plus All Super Bot Fight Mode rules if your plan has it.
- Save and deploy, then try publishing again.
On Cloudflare’s Free plan? Bot Fight Mode lets verified bots like RightBlogger through, so you shouldn’t need to change it. It can’t be skipped with a custom rule, though, so if publishing is still blocked after the steps above, turn it off as a test: open your Cloudflare Security settings (older dashboards: Security > Bots) and switch Bot Fight Mode off. Paid plans use Super Bot Fight Mode: check that Verified bots is set to Allow, or use the skip rule above.
If you use a different firewall or security plugin (Wordfence, WP-SpamShield, or a host-level firewall), allow the same user agent and specific path together there instead.
A firewall can also drop the request without a 403. If the error says RightBlogger “could not open a connection” to your site, or that your site “accepted the connection and then closed it before replying”, ask your host to allow the same user agent and path.
Because RightBlogger requests can come from rotating cloud IP addresses, use the user-agent and path conditions together rather than a fixed IP. A user-agent alone can be copied, and a path-only rule would expose more of your WordPress REST API than necessary.
After changing rules you can use the “Check connection” button in the integrations tab of your project to verify if RightBlogger can talk to the plugin.

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 these steps and still can’t connect, email contact@rightblogger.com and we’ll help you sort it out.
Related Guides
Still need help?
Ask the AI assistant for an instant answer, or reach us directly and we will get back to you as soon as we can.
Automated SEO Blog Posts for Your Site
Research, write, publish, and share from one account.
7-day free trial. Cancel anytime.




