Skip to content

Tailnet Status

Jump to bottom
koppot edited this page Oct 20, 2026 · 1 revision

Tailnet Status

Nebulae embeds Tailscale and connects this machine to a private encrypted mesh network (the ADC Tailnet). This gives your torrent engine a direct, private path to ADC infrastructure — tracker, ratio API, and related services — without those requests ever touching the open internet.

How it works

  1. On first launch Nebulae enrolls the machine as a Tailnet node and assigns it a private IP in the 100.64.x.x range.
  2. A local SOCKS5 proxy starts on 127.0.0.1:1055.
  3. The Transmission engine routes tracker and ADC API traffic through that SOCKS proxy.
  4. Traffic traverses the WireGuard-encrypted Tailnet to the ADC peer, rather than your regular internet connection.

Status indicators

The Tailnet entry in the Status Bar shows the live state. See the Status Bar page for the full indicator table.

Persistence

  • Enrollment persists across application restarts, macOS sleep/wake, and supervisor restarts.
  • You do not need to re-enroll after a normal quit and relaunch.
  • The embedded daemon is supervised: if it exits unexpectedly, the supervisor restarts it and re-establishes the connection automatically.

Troubleshooting

Symptom Likely cause What to do
ADC unavailable (amber) ADC peer not visible in tailnet Check that the tailnet is healthy and the ADC peer is online
ADC unverified (grey) Probe has not completed yet Wait up to 10 minutes; probes run on a timer
ADC host offline (amber) Probe failed on the private route Verify route acceptance is active; check tailscale status from a terminal
Tailnet not connected Daemon stopped or enrollment expired Restart Nebulae; the supervisor restarts the daemon automatically

Note

The Tailnet status only reflects whether the private route to ADC is working. It is not a general-purpose VPN indicator for all of your internet traffic.

Next: Media Center

Clone this wiki locally