Feature Request: Bring Your Own Domain
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 669
- Forks
- 61
- Avg merge
- 6d 6h
- Merged PRs (30d)
- 3
Description
I'd quite like to expose my TSIDP over the internet with my own domain. Unfortunately the client will only bind to localhost, ruling out a reverse proxy.
I then went on to try to proxy my domain -> ts.net via funnel, but this is also blocked by the client as I'm not connecting to the tsnet domain.
Could there please be a way to either bind to a different interface, or bring your own domain another way?
The only other solution I can think of is to enable localhost binding, and use "network_mode: service:idp_proxy" to forward the traffic from my chosen interface to localhost. Otherwise I have to build from source. Both options are tedious and 'hacky'.
I may have missed a way to do this already implemented. If so, I welcome suggestions.
Thanks
Contributor guide
No contributing guide indexed for this repository
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
No source file, test, or entry point is identified in the issue. Start by locating the localhost binding and the client check that rejects connections through a custom domain or ts.net funnel. Compare the requested approaches and establish which supported exposure behavior defines completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100