MCP OAuth Discovery Documents

  • wpconvert

    (@wpconvert)


    9 hours, 44 minutes ago

    I have this error in Site Health on all sites that updated to Rank Math 1.0.278:
    Obviously, this will also be appearing in my error logs.

    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.

    Rolling back to 1.0.277.1 eliminates the error. Do you intend to provide a switch/toggle to disable MCP connector functionality?

You must be logged in to reply to this topic.