tom/food
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

nginx: 404 the .well-known/ OAuth probes for the MCP connector

Browse Source 
claude.ai's custom-connector flow probes /.well-known/oauth-* during
setup. The catch-all 301 -> /app/ made those return the Kitchen login
page (200), so claude.ai mistook it for an OAuth sign-in service, tried
Dynamic Client Registration, and failed. Returning 404 makes it treat
the server as authless and connect.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Tom Flux
2026-06-23 21:41:41 +01:00
co-authored by Claude Opus 4.8
parent 90239baada
commit 77b42a8758
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/food.tomflux.xyz.nginx
+7
View File
@@ -44,6 +44,13 @@ server {
proxy_read_timeout 3600s; proxy_read_timeout 3600s;
} }
# OAuth-discovery probes MUST 404, not fall through to the /app/ login
# redirect. Otherwise claude.ai's connector flow sees the login page at
# /.well-known/oauth-* , thinks the server has an OAuth sign-in service,
# tries Dynamic Client Registration, and fails ("Couldn't register with
# ... sign-in service"). A 404 here makes it treat the server as authless.
location /.well-known/ { return 404; }
location / { location / {
return 301 /app/; return 301 /app/;
} }