Skip to main content

Troubleshoot WordPress Connection Issues

Updated over a month ago

In this article, we’ll go over the most common WordPress connection issues and how to fix them quickly.

Wrong WordPress URL

Make sure to specify the correct URL for your blog. Please be sure to take care if your blog is installed on a subdomain (like https://blog.domain.com) or in a folder (like https://domain.com/blog).

A good way to test if the URL is correct is to simply add /wp-json at the end of the URL, like this https://domain.com/wp-json. If the URL is correct, you should see some JSON code displayed.

Application Password

Using the user password instead of the Application Password

One of the most frequent mistakes is using the regular user password instead of an Application Password.

Application Passwords usually have the following format:

m5yt A13k b2tf 4PAV zrta VAwB

Cannot find the Application Password in the user profile

If you cannot find the Application Passsword section in the user profile, this may be due to different reasons:

Issue

Possible Cause

Solution

Not visible at all

WordPress version < 5.6

Update WordPress to 5.6 or later.

Not visible on the HTTP site

Requires HTTPS by default

Please make sure HTTPS is enabled.

Section hidden or disabled

Plugins like Wordfence or JWT plugin are interfering

Check and adjust plugin settings, or deactivate temporarily to test.

Not available to the user

Non-admin user role

Please make sure you are logged in as an administrator and check role restrictions.

User permissions

Make sure the WordPress user has editor or administrator permissions.

Plugins interfering

Some WordPress plugins may interfere:

Plugin

Solution

Really Simple SSL

Turn off the Settings -> Hardening -> Basic -> Disable user enumeration or disable the plugin.

WordFence

Review settings related to Application Passwords functionality, as blocking this feature can cause problems.

Disable WP REST API

Uninstall this plugin or any similar plugin that blocks access to REST API.

LiteSpeed Cache

Check that you haven't restricted access to the /wp-json endpoint in the settings.

Did this answer your question?