Skip to content

Conversation

@khartahk
Copy link

@khartahk khartahk commented Dec 20, 2025

  • add global tailscale.port option
  • added proper handling for default node:
    If no name is specified it used hardcoded string "caddy" but the docs
    say that it is using the binary name

When bind tailscale/ is used without a node name, Caddy's network address parser returns an empty string for host, and the code was passing that empty string to getNode("") which would create a node with no proper name, causing Tailscale to auto-generate a conflicting name like caddy-1 and use a random port instead of the configured global port.

I've built it locally and tested that it works for my use case.

  • So tailscale.port sets the port to the global nonamed node
  • tailscale.<SERVER>.port sets it like normaly for the <SERVER>

- add global tailscale.port option
- added proper handling for default node:
  If no name is specified it used hardcoded string "caddy" but the docs
  say that it is using the binary name

Signed-off-by: khartahk <khartahk@users.noreply.github.com>
@khartahk khartahk force-pushed the globa-config-port-for-default-node branch from edcffe0 to 968fa2a Compare December 20, 2025 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant