getting "Error creating connector" on ChatGPT.com

[jplew]

Hi, I'm using Tailscale Funnel to create my tunnel. I ran init and serve without issue.

But when it came time to register my MCP server I got this error:

I see this in my server logs:

Am I doing something wrong?

[jplew]

never mind, it looks like the problem was related to Authentication. I switched to OAuth instead of No Auth and it worked. I think that's worth mentioning in the docs.

This is amazing!

[aaamosh]

We tested DevSpace today through Tailscale Funnel as well. Short field report in case it helps the docs or the next release:

• ChatGPT app creation/connection worked for us when using OAuth, not No Auth.
• The public metadata endpoint returned 200 and /mcp correctly returned a 401 Bearer challenge before authorization.
• After OAuth approval, ChatGPT connected and OpenAI MCP traffic reached DevSpace successfully.

One Tailscale-specific gotcha we hit: Funnel sends proxy headers such as X-Forwarded-For. With the current boolean DEVSPACE_TRUST_PROXY behavior, Express/rate-limit can warn about forwarded headers unless trust proxy is enabled. Locally, the safer shape for us was to allow DEVSPACE_TRUST_PROXY=loopback and pass that through to app.set("trust proxy", "loopback"), instead of only supporting all-or-nothing boolean trust. That kept request IP/rate-limit behavior clean for the local Funnel proxy path without trusting arbitrary upstream proxy headers.

So for Tailscale Funnel setups, the docs probably want to emphasize OAuth mode, and the implementation may eventually want a non-boolean trust-proxy option (loopback, hop count, etc.).