connector 404

[jhmonroe]

When trying to setup the Claude connector, using the third claude method of providing oauth info from google I get a 404 page in openseo (self-hosted) at the final step

First it takes me to a claude page that says "Finish connecting a connector?"

I click continue, it takes me to a url that looks like:

openseo.mydomain.com/authorize?oauthstringhere

yields "404
The page you are looking for does not exist."

if i used the detected/auto settings it yields:

"Couldn’t register with OpenSEO’s sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support:...."

[jg-noncelogic]

That 404 most likely means the OAuth request is reaching OpenSEO itself instead of the expected auth layer. On current main, self-hosted OpenSEO serves MCP at /mcp; it does not mount an OpenSEO application route at /authorize (routing, self-host transport).

If this deployment is behind Cloudflare Access:

1. Configure the Claude connector with https://openseo.mydomain.com/mcp, not the site root.
2. In the Access application covering that hostname/path, enable Additional settings → OAuth → Managed OAuth.
3. Allow Claude's exact HTTPS redirect URI in that Managed OAuth configuration.
4. Remove and re-add the connector so Claude does fresh OAuth discovery.

Those are also the repository's self-host MCP instructions. Cloudflare describes Managed OAuth as the layer that supplies OAuth to non-browser clients such as MCP clients: https://developers.cloudflare.com/cloudflare-one/access-controls/applications/http-apps/managed-oauth/

If this is Docker/private local_noauth instead, there should be no browser OAuth flow at all. OpenSEO handles /mcp directly in that mode, so a Claude connector that insists on OAuth needs an OAuth-capable front door rather than a new /authorize route in OpenSEO.

If the steps above do not fix it, the two useful details are the deployment/auth mode (cloudflare_access or local_noauth) and whether the 404 is visibly OpenSEO's page or Cloudflare's. Please redact the complete /authorize?... URL, OAuth parameters, cookies, and tokens.

AI-generated and source-checked against the pinned OpenSEO code and documentation above.

[jhmonroe]

@jg-noncelogic thanks

It's self-hosted in Docker on Vultr VPS. My agent (Claude) had originally suggested placing the main site behind a simple browser user/password since it's publicly accessible. Turns out that was the issue. Had to carve out an exception it.

Do you think this browser protection was overkill generally? Since I'm only allowing Google OAuth from my ONE Google login, in theory this means no one else can use the site or burn thru credits...