WordPress - MCP OAuth discovery documents

Jon Snow · Sep 17, 2026 at 6:15 AM

Hi @eva2000

Does your wpsecure.conf file need adjustments for the new Wordpress 7.1 version?

MCP OAuth discovery documents

The following .well-known discovery document(s) did not respond as expected: oauth-protected-resource, oauth-authorization-server. This does not match the confirmed .well-known/acme-challenge/ interception fingerprint, so the cause is inconclusive from this check alone (it may be a timeout, an access wall such as HTTP Basic Auth or a WAF, or a WordPress-served error).

Check your error/access logs for the requests to these paths, and rule out an authentication wall (staging HTTP Basic Auth, a WAF, or bot mitigation) before assuming a routing problem.

This check runs from the server to itself. A "Good" result here does not guarantee external clients can reach these documents: a CDN, WAF, or reverse proxy in front of the site can still 404 these paths for external traffic while the server's own loopback request bypasses it. Verify with an external curl request after applying any server-config change.
Click to expand...

From Wordpress Site Heath Report /wp-admin/site-health.php

Log in / Register

Forums

Discover Centmin Mod today

WordPress - MCP OAuth discovery documents

Jon Snow Active Member

.

Log in / Register

Useful Searches

Discover Centmin Mod today

WordPress - MCP OAuth discovery documents

Jon Snow Active Member

.