• Resolved jeff4022

    (@jeff4022)


    I actually have gotten very close to getting OAuth working by disabling all plugins (including SG Security), changing templates, adding the cloudflare header transform rule,.  All the curl requests seem to be returning properly (except that I see content-type i still text/plain and i think that should be returning json? Not sure.  I even had OAuth connected!

    But then I started to add plugins back (retrying the connection after each time).  Somewhere along that way, I am now at the point when I try to connect and it pulls up your authorization window – it is not writing the URL properly (see the two https’), and if I delete one of them so the URL is correct, it goes back to failing the connection – on a completely barebones / no plugins installed wordpress instance.  AHHHHHH. Oh and I was never successful with the API KEY method thus far after creating the JSON file and working with support back and forth multiple times until they stopped responding. Cant seem to get claude to read the JSON file which was confirmed to be correct. Anyhow, Ive gotten closer with OAuth than the API KEY method oddly is kind of my point.

    C:\Users\Jeff>curl -I https://staging2.nerdsquad.net/.well-known/oauth-authorization-server
    HTTP/1.1 200 OK
    Server: nginx
    Date: Wed, 27 May 2026 17:56:14 GMT
    Content-Type: text/plain
    Content-Length: 626
    Last-Modified: Wed, 27 May 2026 16:28:16 GMT
    Connection: keep-alive
    Vary: Accept-Encoding
    ETag: "6a171ba0-272"
    Remote-Addr: 73.54.63.7
    Cache-Control: no-store,max-age=0
    Accept-Ranges: bytes

    C:\Users\Jeff>curl -sS https://staging2.nerdsquad.net/.well-known/oauth-authorization-server -H "Accept: application/json"
    {
    "issuer": "https://staging2.nerdsquad.net",
    "authorization_endpoint": "https://https://staging2.nerdsquad.net/authorize",
    "token_endpoint": "https://https://staging2.nerdsquad.net/token",
    "registration_endpoint": "https://https://staging2.nerdsquad.net/register",
    "response_types_supported": ["code"],
    "grant_types_supported": ["authorization_code", "refresh_token"],
    "token_endpoint_auth_methods_supported": ["none", "client_secret_post"],
    "code_challenge_methods_supported": ["S256"],
    "scopes_supported": ["mcp:full"],
    "service_documentation": "https://royalplugins.com/support/royal-mcp/"
    }

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support rpteam

    (@rpteam)

    Glad to report we got this connected and working. Sharing the two issues we
    identified — both fixed now — in case anyone else lands here with similar
    symptoms.

    Issue 1: ambiguous placeholder in our SiteGround static-files walkthrough

    Our /.well-known/ 404 fix walkthrough
    (https://royalplugins.com/support/royal-mcp/siteground-well-known-404.html) used
    YOUR-DOMAIN.com as a placeholder inside the JSON template. The intent was “swap
    with your bare domain,” but a reasonable reading was to swap with the full URL
    https://yoursite.com — which produced https://https://yoursite.com/authorize
    (etc.) in the saved static file. Browsers then parse the resulting URL with
    https as the hostname, DNS lookup fails, and you get a
    DNS_PROBE_FINISHED_NXDOMAIN / “site can’t be reached” page when OAuth tries to
    redirect.

    If you see doubled https://https:// on any of the OAuth endpoint URLs in your
    /.well-known/oauth-authorization-server response, edit your static files and
    remove the duplicates. We’ve patched the walkthrough to use a literal
    example.com placeholder with explicit “do NOT include https:// in your
    replacement” guidance and a verification step, and swept the same fix across the
    rest of our support docs so this shouldn’t trip anyone else.

    Issue 2: Microsoft Store version of Claude Desktop uses a sandboxed config path

    If you installed Claude Desktop from the Microsoft Store, it’s sandboxed and
    reads/writes config from
    %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\ — NOT
    the standard %APPDATA%\Claude\ that every Anthropic doc and our own walkthroughs
    reference. Manual edits to the config at the standard path get silently ignored, restart Claude Desktop all you want, nothing picks up.

    Two fixes:

    RP Team

    • This reply was modified 3 weeks, 3 days ago by rpteam. Reason: typo
Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.