t3 serve --mode web: can't sign in to T3 Connect from localhost
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Open http://127.0.0.1:3773 in a browser: Connect UI renders, but Clerk never loads — no sign-in button, no environments, all silent (controls gate on isLoaded).
Console:
Clerk: Production Keys are only allowed for domain "t3.codes".
The Request HTTP Origin header must be equal to or a subdomain of the requesting URL.
Clerk's prod-key domain lock — allowed_origins doesn't cover browser origins, and a dev instance's tokens won't verify against the production relay. So hosted app and desktop work, but a browser on a self-hosted server is local-only for Connect.
Worth documenting, or is there a supported pattern you'd point people to?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the t3 serve --mode web path and reproduce the behavior at http://127.0.0.1:3773, checking the reported Clerk console errors. Confirm whether a supported localhost or self-hosted pattern exists; done means documenting the limitation and the recommended path, or clearly stating that none is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100