tailscale-mosh-recover

Restore Mosh connectivity on headless Mac mini after Tailscale updates.

127|22|Updated Feb 20, 2026

Search Tags:#remote access #Tailscale #headless #session recovery #Mosh

Ready to run

npx skills add https://github.com/flonat/flonat-research --skill tailscale-mosh-recover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tailscale-mosh-recover
Source: https://github.com/flonat/flonat-research/tree/main/skills/tailscale-mosh-recover
Command: npx skills add https://github.com/flonat/flonat-research --skill tailscale-mosh-recover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tailscale, mosh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses connectivity issues with Mosh sessions on headless Mac mini after a Tailscale update or restart, ensuring seamless remote access.

Core Features & Use Cases

Tailscale Daemon Health Check: Ensures the Tailscale daemon is functioning correctly on headless Mac mini.
Mosh Server Cleanup: Removes stale mosh-server processes bound to old Tailscale IP addresses.
MacOS Resolver Flush: Clears DNS cache to resolve new Tailscale IP addresses.
Direct-IP Fallback: Bypasses relay servers for direct connections when necessary.
Use Case: After updating Tailscale on a headless Mac mini, Mosh sessions fail to connect. This Skill can be used to quickly recover and reconnect.

Quick Start

Run the skill to recover your Mosh session with the command: use tailscale-mosh-recover recover

Frequently Asked Questions about tailscale-mosh-recover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I recover a Mosh session on a headless Mac mini after a Tailscale update?▼

Recover your Mosh session by running a health check on the Tailscale daemon, cleaning up stale mosh-server processes bound to old IP addresses, and flushing the DNS cache to resolve the new Tailscale IP addresses.

Why does Mosh fail to connect after restarting Tailscale on a headless Mac?▼

Mosh fails to connect after a Tailscale restart because stale mosh-server processes remain bound to old Tailscale IP addresses and the macOS DNS cache lacks the updated routing information.

How do I clean up stale mosh-server processes bound to old Tailscale IP addresses?▼

Clean up stale mosh-server processes by running a recovery script that identifies and removes the orphaned processes, allowing Mosh to establish fresh connections using the newly assigned Tailscale IP addresses.

Can I bypass Tailscale relay servers to force a direct connection for Mosh?▼

Yes, you can bypass Tailscale relay servers by using a direct-IP fallback mechanism, which forces Mosh to establish a direct connection to the headless Mac mini when relay routing is inefficient or blocked.

Does the Mosh recovery process require any specific macOS network utilities?▼

Yes, the Mosh recovery process requires specific macOS network utilities to flush the DNS resolver cache, alongside active installations of both Tailscale and mosh to properly restore headless remote access connectivity.

What is the best way to restore remote access to a headless Mac mini when Tailscale updates drop the connection?▼

Restore remote access by executing an automated recovery sequence that checks the Tailscale daemon status, clears stale Mosh processes, flushes the macOS DNS cache, and applies a direct-IP fallback if necessary.