Skip to main content
Most failed connections never reach WordPress. A web server rule, a firewall or a proxy answers the app’s request first, so the Dashboard has nothing to show. Two tools in MainWP > AI > MainWP MCP > Connect directly find these problems:
  • Run the self-test checks the Dashboard from the Dashboard itself. It makes requests to its own public addresses, so it sees what the server in front of WordPress does with them, but not what an app on the internet sees.
  • Check from the internet asks MainWP’s checker to test your Dashboard from outside. It sends only your Dashboard’s address, one request per click, and nothing is stored.
Each line has a status: pass, warn, fail, info or skipped. Some lines show a fix below the message, and some link to What to check.

Host guides

When the Dashboard recognizes your host or security plugin, its help links go to the matching guide:

WP Engine

Managed WordPress hosting.

Kinsta

Managed WordPress hosting with a CDN in front.

Cloudflare

Proxy, CDN and firewall.

Wordfence

Security plugin with a firewall.

Sucuri

Security plugin and cloud firewall.

Solid Security

Security plugin, formerly iThemes Security.
The Dashboard recognizes them from local signals only: WP Engine and Kinsta from their server settings, Cloudflare from the CF-Ray header on your own admin requests, and the security plugins when they’re active. For anything else, the links come to this page.

An app hasn’t reached the Dashboard

If no request arrives within 10 minutes after you approve a connection or create a connection token, the panel shows a line such as:
Claude hasn’t reached this Dashboard yet.
with a What to check on your host link. You approved in your browser, which reached the Dashboard, but the app’s own requests didn’t. Run Check from the internet, then look at the connection’s row under Connections:
  • Last request shows the time of the app’s last successful request, or Never.
  • The IP address below it is where that request came from.
  • Last failure shows a reason code and its time when the Dashboard refused a request it could match to this connection. Common codes are invalid_grant (the app’s sign-in expired or was replaced; sign in again from the app), wrong_resource (the permalink mode changed after the app connected), cap_lost (the user lost manage_options), unknown_client (the app was switched off or removed), insufficient_scope (a view-only connection tried a change) and activity_log_off.
A request the Dashboard can’t match to any connection only shows up in the self-test’s 24-hour counters.

Self-test lines

Scope

These checks run from the Dashboard itself, so they can’t see what Claude, ChatGPT or another app sees from the internet. Use “Check from the internet” for that.
This info line always appears first.

PHP and WordPress

HTTPS site address

Your site address starts with http://. Remote AI connections need https://.
Change the site address in Settings > General (or the WP_HOME constant) to https://, after the site has a working certificate. Changing the site address ends every existing connection.

Activity log

Turn on the activity log first. AI apps can’t make changes or use tools MainWP hasn’t reviewed unless each call is recorded.
Turn on Enable Network Activity logging under MainWP Settings > Network Activity Settings. This line blocks turning the connector on.

Kill switch

Remote AI connections are turned off on this site by the MAINWP_DISABLE_REMOTE_MCP setting in wp-config.php.
or “…by a plugin.” Someone forced the connector off. See the kill switch to find and remove it.

Another plugin serves the well-known addresses

Another plugin serves /.well-known/oauth-authorization-server through a rewrite rule. Two sign-in servers can’t share that address, so remote AI connections can’t be turned on.
Another OAuth or OpenID Connect plugin answers the address every app asks first. Turn off that plugin’s sign-in server, or deactivate the plugin, then run the self-test again.
Another plugin serves /.well-known/openid-configuration. Apps that look there first may find that plugin instead of this Dashboard.
This is a warning. Apps that ask for /.well-known/oauth-authorization-server first still find the Dashboard.

Port other than 443

Remote AI apps may not reach port 8443.
Your site address includes a port other than 443. See Ports other than 443.

Requests for the well-known addresses

Requests for the well-known addresses don’t reach WordPress, so no app can find how to sign in.
The web server answers /.well-known/oauth-authorization-server and /.well-known/openid-configuration itself instead of passing them to WordPress. The fix line below the message depends on your permalinks:
  • With plain permalinks: “Turn on pretty permalinks in Settings > Permalinks, or add this rule to the .htaccess file of this WordPress install”. See Plain permalinks.
  • Otherwise: “Ask your host to send these addresses to WordPress, or add this rule to the .htaccess file of this WordPress install”.
The rule for a Dashboard at the root of its domain is:
For a Dashboard in a subdirectory such as /dashboard, the self-test shows the path in the rule: /dashboard/index.php. On nginx, see nginx rules.

Which apps can find the sign-in information

The self-test fetches the four forms of the well-known addresses and replays the order in which Claude Code, Claude, VS Code and ChatGPT were seen asking for them. Each line names the affected apps. The self-test doesn’t judge other apps, but they read the same addresses.

Subdirectory installs

On a Dashboard in a subdirectory, apps can find it at /dashboard/.well-known/… without a server rule. When that form is blocked too, the self-test shows one of:
https://your-dashboard.com/dashboard/.well-known/oauth-authorization-server is answered by another WordPress install, so the request never reaches this Dashboard. A server rule that blocks addresses starting with a dot usually causes this.
The web server blocks https://your-dashboard.com/dashboard/.well-known/oauth-authorization-server before it reaches WordPress. A server rule that blocks addresses starting with a dot usually causes this.
followed by:
Add this rule to the web server in front of your site so apps find this Dashboard at the root well-known addresses.
with the rule for your path. See nginx rules.

Something other than WordPress answers

Something other than WordPress answers https://your-dashboard.com/.well-known/openid-configuration, for example a static file or a server rule. Remove it so these addresses reach WordPress.
A file with that name exists on disk, or a server rule returns a fixed response. Remove it, or ask your host to.

Authorization header

The Authorization header doesn’t reach WordPress: the web server or a proxy strips it, so every app request looks signed out.
Every app request carries its token in the Authorization header. Some Apache and CGI setups drop it before PHP. The fix line reads “On Apache, add “CGIPassAuth On” to the .htaccess file, or ask your host to pass the Authorization header to PHP.” Add this near the top of the .htaccess file of the Dashboard’s install:
If your server refuses CGIPassAuth (it needs Apache 2.4.13 or later), this line passes the header as an environment variable instead:
On other servers, ask your host to pass the Authorization header to PHP.

HTTPS as WordPress sees it

Requests reach WordPress as http://; see the reverse proxy guide.
A proxy, load balancer or CDN handles HTTPS and talks to WordPress over plain HTTP, so WordPress can’t tell the request was secure. The Dashboard refuses those requests. The What to check link opens WordPress’s guide to HTTPS behind a proxy. The usual fix is this block in wp-config.php, above the line that says to stop editing:
First confirm that credentials remain encrypted between the client, proxy, and origin. This block only tells WordPress how the request arrived; it does not encrypt an HTTP connection. Add it only when every request reaches WordPress through that trusted proxy, and the proxy always sets X-Forwarded-Proto itself. If visitors can reach the server directly, anyone can send that header. The Dashboard never reads it on its own for that reason.

The probe didn’t reach WordPress

The probe of the MCP address didn’t reach WordPress.
The self-test’s request to the MCP address got no answer from WordPress: a timeout, a block page, or an error from the server in front. This line shows twice, once for the header check and once for the HTTPS check. Check the server’s error log and any firewall, then run the check from the internet.

Plain HTTP

A plain http:// request to the MCP address was answered. It must be refused.
Something answers http:// requests to the MCP address with a success response. Set the server to redirect http:// to https:// or refuse it. The pass line reads “Plain http:// requests to the MCP address are refused.”

Counters for the last 24 hours

Last 24 hours: requests without an Authorization header: 3; tokens rejected: 0.
Every app’s first request has no Authorization header, so a count here is normal. The line only warns when no request has arrived with the header in the last 24 hours: “No request with an Authorization header has reached WordPress in the last 24 hours. If an app can’t connect, the web server or a proxy may be stripping it.” See Authorization header. Rejected tokens are usually expired or revoked connections that the app keeps trying.
Unknown apps refused in the last 24 hours: 2.
Requests from apps the Dashboard doesn’t know. Anyone can send these, so a small number is normal. If your app is counted here, check that it’s in Set Up Your AI App and that its switch is on.

Bundled app files

These apps can’t connect because their bundled file failed its check: ChatGPT. Reinstall or update MainWP.
The Dashboard ships a file with each known app’s sign-in details and checks it before use. A partial update or an edited file fails the check. Reinstall or update MainWP Dashboard. Remote AI connections work with plain permalinks. The panel shows the MCP address in its query form, https://your-dashboard.com/?rest_route=/mainwp-remote/v1/mcp, and the sign-in and approval pages use ?mainwp_oauth= addresses. The well-known addresses still have to reach WordPress. On Apache with plain permalinks there is no WordPress block in .htaccess, so they don’t, and the self-test fails the well-known line. Either:
  • turn on pretty permalinks in Settings > Permalinks, or
  • add the rule from the self-test’s fix line to the .htaccess file.
On nginx, WordPress configurations usually pass unknown paths to index.php whatever the permalink setting. If you switch permalink modes later, the MCP address changes, and every app has to connect again.

nginx rules

This section covers both nginx and Apache. On nginx, a rule that denies paths starting with a dot (often location ~ /\.) also blocks /.well-known/… and /dashboard/.well-known/…. For a Dashboard in a subdirectory, use both rules below in the server block, before the location blocks, with your path in place of /dashboard. The first covers the root discovery form; the second covers the subdirectory form:
The self-test also shows the Apache form, labeled as untested, for the .htaccess file at the root of the domain:
For a Dashboard at the root of its domain, the same form without the path sends the two addresses to WordPress:
The rewrite keeps the original address, which is what the Dashboard reads. Reload nginx after the change, then run the self-test again. On managed hosting where you can’t edit the nginx configuration, send the rule to your host’s support.

Ports other than 443

If your site address includes a port, for example https://your-dashboard.com:8443, every address the Dashboard gives apps includes that port. The self-test shows “Remote AI apps may not reach port 8443.” as a warning and still lets you turn the connector on. Apps on your own computer usually reach any port. Hosted apps such as Claude and ChatGPT connect from their own servers, and support for other ports hasn’t been confirmed. Serving the Dashboard on 443 avoids the question. If you must use another port, test with Check from the internet and with the app itself.

Check from the internet

The checker tests five things in order: DNS, TLS, discovery of the sign-in information, the sign-in information itself, and the MCP address. After a check fails, the checks after it are skipped. A passing check reads “Passed.” Failing and warning lines link to the host guide. If the checker can’t run, or you run it too often, the panel shows “The check from the internet couldn’t run. Try again in a few minutes.” The checker accepts 10 checks per hour from one address.

Still stuck

  • Run the self-test and the check from the internet again after each change. Some hosts cache server rules for a few minutes.
  • If your host manages the web server, send them the failing lines and the rules on this page.
  • The local MCP server works as a fallback. It needs only HTTPS from your computer, not the well-known addresses or a Dashboard reachable from the internet.