Distinguish between internal and external IP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Dokploy connects to remote servers over private IP.
The public IP used for DNS is different.
Right now I only set the internal IP and this doesn't seem to cause any critical issues, the DNS Check however fails and the auto-generated traefik.me domains use the wrong internal IP by default.
Describe the solution you'd like
A Remote Sever should be able to have both a public and private IP.
Describe alternatives you've considered
No relevant alternatives. I dont want them on public Network, one alternative I have in mind is Tailscale, that would however require the same kind of distinguishment between a nodes public and private endpoint.
Additional context
No response
Will you send a PR to implement it?
Maybe
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 by tracing how Dokploy stores remote-server connection details, performs DNS checks, and generates traefik.me domains. Identify the relevant server model and DNS/domain entry points, then verify how each currently uses the internal IP. Done means a remote server can retain distinct private and public IPs without exposing its private network, with DNS checks and generated domains using the public address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100