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

未关闭
#80 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@viniciusbregoli 已经在做这个了。

开始于 2026年11月18日。

  • #82 来自 @viniciusbregoli —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
bash, shell
领域
devops

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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)

主要语言
TypeScript
星标
277
派生
27
平均合并
2 小时 47 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DuskBotAI/duskbot 的其他 Issue

查看 DuskBotAI/duskbot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。