Troubleshooting

One-shot diagnostics (recommended)

When troubleshooting anything — or before opening an issue — run:

tailscale-manager diagnostics

It collects the versions, device/system info, install and runtime state, dependency checks, UCI config, and recent log excerpts in a single block you can paste straight into a GitHub Issue (doctor is an alias).

If you only want the logs:

tailscale-manager logs        # manager, service, and system logs at once (last 200 lines)
tailscale-manager logs 500    # custom line count

Log Files

Log	Location	Content
Manager log	/var/log/tailscale-manager.log	Install, update, uninstall, rollback, and script operations
Service log	/var/log/tailscale.log	Tailscale daemon output
Auto-update log	/var/log/tailscale-update.log	Scheduled Tailscale binary updates (cron)
System log	logread -e tailscale	procd service events

Logs live under /var/log (usually tmpfs) and are wiped on reboot.

To keep the manager log across reboots, set the LOG_FILE environment variable to a persistent path, e.g.:

LOG_FILE=/etc/tailscale/manager.log tailscale-manager status

Common Issues

Service fails to start at boot

Symptom: Tailscale doesn't start after reboot.

Possible causes:

• Network not ready yet (common with OpenClash or other proxy tools)
• Binary not found (RAM mode + no internet at boot)

Solution: The init script has built-in retry logic — 10 retries at 30-second intervals (5 minutes total). Check logs:

logread | grep tailscale
cat /var/log/tailscale.log

Cannot connect to HTTPS endpoints

Symptom: wget fails with SSL errors.

Solution: Install SSL support:

opkg update
opkg install wget-ssl libustream-mbedtls ca-bundle

TUN device not available

Symptom: tailscaled starts in userspace mode unexpectedly.

Solution: Install the kernel TUN module:

opkg update
opkg install kmod-tun
modprobe tun

Insufficient disk space

Symptom: Installation fails with disk space errors.

Solution: Use Small binary source (~8-10 MB) or RAM storage mode:

tailscale-manager install
# Choose "Small" source and "RAM" storage

Service is running but not reachable

Symptom: tailscale status shows connected, but devices can't reach local services.

Solution: Set up subnet routing:

tailscale-manager setup-subnet-routing
tailscale set --advertise-routes=192.168.1.0/24

Then approve the route in the Tailscale Admin Console.

Getting Help

• GitHub Issues — Report bugs or request features
• Before filing an issue, attach the full output of tailscale-manager diagnostics
• Run tailscale-manager status for a quick install/runtime overview