Servers & Self-Hosting
6 curated resources, easiest first.
Clear walkthrough for creating an Ed25519 SSH key pair, protecting it with a passphrase and loading it into ssh-agent on Linux, macOS and Windows. It is written for GitHub, but the key generation and agent steps apply to logging in to your own servers with keys instead of passwords.
Shows how to create a private tailnet by installing the Tailscale client on two devices and signing in with the same identity account, then points to follow-ups like MagicDNS, exit nodes, subnet routers and access policies. A VPN-style overlay like this is a safer way to reach home services than opening ports on your router.
Microsoft's steps for changing the RDP listening port from the default 3389 using PowerShell or the Registry Editor. Moving the port is a configuration tweak, not real protection, so still keep RDP off the public internet and reach it through a VPN such as WireGuard or Tailscale.
Explains how one Tailscale device can advertise a whole LAN so you can reach printers, cameras or a NAS that cannot run the client. You need IP forwarding on the router device, approval of the routes in the admin console, and access rules that permit the traffic. Approving a route does not grant access by itself.
The poster moves Pi-hole onto its own Tailscale node by sharing the Tailscale container's network (network_mode: service:tailscale) and tagging it. The caveat reported is that query logs then show all requests from localhost instead of the real clients, and the thread is an open question rather than a settled solution.
The project's own quick start: generate a private and public key pair with the wg tool, create a wg0 interface, assign an address, configure a peer, bring it up and verify with wg show. Keep the private key file readable only by you.