tailscale-homelab

SSH into Tailscale-routed homelab hosts using standardized aliases and identity-file conventions.

1|Updated Mar 18, 2024
One-click install
npx skills add https://github.com/erfianugrah/dotfiles --skill tailscale-homelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailscale-homelab
Source: https://github.com/erfianugrah/dotfiles/tree/main/.pi/agent/skills/tailscale-homelab
Command: npx skills add https://github.com/erfianugrah/dotfiles --skill tailscale-homelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably reach and operate homelab hosts across multiple sites using Tailscale, even when DNS, routing paths, or SSH keys behave differently between primary and backup connectivity.

Core Features & Use Cases

  • One-alias homelab access: Uses SSH aliases aligned to the host inventory so you can run container and file operations on the main Unraid server without knowing the current network path.
  • Subnet and site-to-site conventions: Explains the dual LAN alias pattern (10.0.X.Y and 10.68.X.Y) for primary vs backup IPsec tunnels, plus Tailscale subnet router behavior and required IP forwarding.
  • Tailscale diagnostics that match reality: Provides a practical, ordered failure-mode checklist (especially for WSL2) that starts with SSH liveness and then validates tailnet IP resolution, MagicDNS, and key offering.
  • Exit-node and ACL correctness: Covers how via: grants and subnet-route approvals affect connectivity, so debugging focuses on the right control-plane constraints.

Quick Start

Tell the assistant to help you SSH to the homelab host alias and provide the next diagnostic step if SSH fails, using the failure-mode order documented for WSL2.

Frequently Asked Questions about tailscale-homelab

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

FAQPage Schema
How do I SSH to an Unraid homelab server through Tailscale?

To SSH to an Unraid homelab over Tailscale, use standardized SSH aliases aligned to your host inventory. This allows container and file operations on the main server without manually resolving the current network path.

Why does Tailscale MagicDNS fail to resolve on WSL2 during SSH troubleshooting?

MagicDNS resolution issues in WSL2 require following an ordered failure-mode diagnostic checklist. Validate SSH liveness first, then check tailnet IP resolution, MagicDNS settings, and SSH key offering to isolate the failure point.

How do I configure Tailscale ACLs for exit-node and subnet routing access?

Configure Tailscale ACLs by verifying `via:` grants and approving subnet routes. Correct exit-node and ACL configurations ensure your debugging targets the right control-plane constraints for reliable connectivity.

Do I need IdentitiesOnly configuration for Tailscale SSH key authentication?

Yes, you need the IdentitiesOnly convention for Tailscale SSH key authentication. Following this identity-file constraint ensures the SSH client offers the correct key, preventing authentication failures across multi-site homelab devices.

Can I manage ARM compute modules and edge devices using Tailscale SSH aliases?

Yes, you can manage ARM compute modules and edge devices using Tailscale SSH aliases. The routing setup applies standardized aliases across multi-site networks to reach OOB management and compute hosts reliably.