install.sh --tailscale replaces whatever the host already serves on tailnet port 443

Open
#80 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@viniciusbregoli is already working on this.

Since Nov 18, 2026.

  • #82 by @viniciusbregoli — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
bash, shell
Domain
devops

Research direction

Start with apps/link-service/install.sh, especially address_tailscale, and inspect uninstall.sh alongside it. The issue points to tailscale serve status --json as the existing-handler check; trace how installation and removal affect port 443 and what state would need preserving. Done means the existing service is not silently lost and uninstall restores the prior configuration; pull request #82 is already open.

Written by the indexing model from the issue text.

Description

What happened

install.sh --tailscale (address_tailscale in apps/link-service/install.sh) runs:

tailscale serve --bg --https=443 "http://127.0.0.1:$PORT"

without checking whether the host already serves something on tailnet port 443. On a host that already uses tailscale serve for other services, this replaces that handler without saying so. uninstall.sh then runs tailscale serve --https=443 off, which doesn't bring the previous handler back either.

I found this while setting up phone access on a host where 443 was already taken by another service, so I didn't run --tailscale there. Instead, I pointed DUSK_PUBLIC_URL at an existing tailscale serve entry on another port.

Suggestions: check tailscale serve status --json first. If 443 is taken, use a free HTTPS port or ask, and pass the actual port to --public-url. Have the uninstaller restore what was there before.

Steps to reproduce
  1. On a tailnet host, run tailscale serve --bg --https=443 http://127.0.0.1:8082 (any existing service).
  2. Run the install line with --tailscale.
  3. tailscale serve status now shows 443 pointing at the dusk bot server. The previous service is gone.
Version

install.sh as served on 2026-11-18 (same ts serve line on main)

Platform

Own server (VPS)

Dominant language
TypeScript
Stars
277
Forks
27
Avg merge
2h 47m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DuskBotAI/duskbot

All issues in DuskBotAI/duskbot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.