Feature requestPending

tailscaled flagged as an unmanaged "app" (Unidentified listener) with a delete button

thanhlinh9191Posted

The problem

Environment
- Server Compass: (desktop, macOS)
- Server: Ubuntu 24.04.5 LTS, arm64
- Tailscale 1.104.1, running as the stock systemd unit tailscaled.service

What happens

The server overview shows a warning card: "1 App and Service Detected — Running outside of
Server Compass — includes system services". The only entry in it is:

  • port tcp/36520 · running
  • Image: Unidentified listener · Project: tailscaled
  • Ports: 36520:36520/tcp, 41641:41641/udp, 41699:41699/tcp
  • A trash (delete) icon next to it

What these ports actually are (ss -tulnp on the server)
udp 0.0.0.0:41641 tailscaled pid=6090
udp [::]:41641 tailscaled pid=6090
tcp 100.64.13.91%tailscale0:41699 tailscaled pid=6090
tcp [fd7a:115c:a1e0::1638:d5c]%tailscale0:36520 tailscaled pid=6090
- 41641/udp is Tailscale's WireGuard port (PORT="41641" in /etc/default/tailscaled).
- 41699/tcp and 36520/tcp are Tailscale's PeerAPI. They are bound only to the tailnet addresses
on tailscale0, and the port numbers are chosen at random each time tailscaled starts.

Problems
1. A system daemon is shown as an unidentified app. The process name (tailscaled) is detected
and used as the "Project", but the entry is still labelled "Unidentified listener" and
grouped with apps "deployed manually or by another tool".
2. The card title is a random port. It shows tcp/36520, a PeerAPI port that changes on every
restart, so the entry keeps looking new and the warning never settles.
3. The delete button is dangerous here. Stopping or removing tailscaled takes the server off the
tailnet. On this host that breaks k3s (flannel runs over tailscale0), monitoring scrapes,
backups to another node, and the fallback SSH path. One click can cut off remote access.

Expected
- Recognise listeners owned by a systemd unit (e.g. from /proc//cgroup →
tailscaled.service) and show them as system services with the unit name, not as unidentified
apps.
- Treat well-known infrastructure daemons (tailscaled, cloudflared, sshd, containerd, k3s, …) as
system services by default, or let the user mark an entry as "known / ignore" so the warning
goes away.
- Name the entry by service, not by its first port.
- Hide the delete action for system services, or require a strong confirmation that names the
unit and warns about losing access.

Steps to reproduce
1. Install Tailscale on an Ubuntu server and run tailscale up.
2. Add the server to Server Compass and open its overview.
3. The warning card lists tailscaled as an unidentified app with a delete button.

Roadmap progress

  1. PENDING

  2. REVIEWING

    —

  3. PLANNED

    —

  4. IN PROGRESS

    —

  5. COMPLETED

    —

  • — thanhlinh9191 submitted this request

Discussion0

Newest first
  • No comments yet. Add context or ask a question below.

Sign in to comment, vote and follow this request.

Sign in to reply