install.sh --tailscale replaces whatever the host already serves on tailnet port 443
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
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
- On a tailnet host, run
tailscale serve --bg --https=443 http://127.0.0.1:8082(any existing service). - Run the install line with
--tailscale. tailscale serve statusnow 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
- 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.
More from DuskBotAI/duskbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageOpen
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 43/100
Maintainers usually reply within 1 day
All issues in DuskBotAI/duskbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day