Essential Homelab Resources, Tools, and Communities

Every guide in this section teaches one specific build. This one is different: it's a map of the wider homelab and self-hosting world -- the communities, reference lists, and tools that come up constantly once you start building your own, collected in one place instead of scattered across a dozen bookmarks. Nothing here is a "you must use this," just a solid, honest starting point.

Step 1: Communities worth joining

• r/homelab -- hardware-focused: builds, rack setups, buying advice, "what should I do with this old server" threads.
• r/selfhosted -- software- focused: what to run, comparisons between similar tools, troubleshooting.
• r/homeassistant and r/PleX / r/jellyfin -- for the two most common "gateway" homelab projects specifically.
• Most self-hosted projects of any size also have their own Discord or Matrix server, usually linked from the project's own GitHub README -- worth joining for the specific software you're actually running, since general communities can't answer project-specific questions as well as the people building it.

Step 2: Reference lists for discovering software

• Awesome-Selfhosted -- a huge, actively maintained, categorized list of self-hostable software alternatives to common cloud services. The single best starting point when you think "there has to be a self-hosted version of this."
• Awesome-Sysadmin -- the sysadmin-tooling equivalent: monitoring, backup, configuration management, and more.
• r/selfhosted's own wiki and "alternatives" megathreads -- community-sourced, opinionated (in a useful way) comparisons that a static list can't capture.

Step 3: Channels and blogs worth following

A few creators who consistently produce accurate, hands-on homelab and networking content, worth knowing by name even if you don't watch regularly: TechnoTim, NetworkChuck, Lawrence Systems, Craft Computing, and LearnLinuxTV on YouTube each cover different corners of this space (Kubernetes/homelab automation, networking fundamentals explained accessibly, enterprise-adjacent firewall/network deep dives, hardware-focused builds, and Linux/self-hosting tutorials, respectively). As with any single source, cross-check anything security- or data-loss-sensitive against the software's own official documentation before acting on it.

Step 4: Official documentation hubs

For anything in this Projects section, the official docs are always the authoritative source the guide itself is based on -- worth bookmarking directly rather than only relying on third-party tutorials: Proxmox VE docs, Docker docs, Pi-hole docs, Home Assistant docs, Jellyfin docs, and OPNsense docs.

Step 5: Tools worth knowing about once you have more than one service

• A reverse proxy (Caddy, Traefik, or Nginx Proxy Manager) -- once you're running more than a couple of web-facing services, a reverse proxy gives each one a real hostname and, for free with Caddy or NPM, automatic HTTPS certificates instead of remembering a different port number for everything.
• Uptime Kuma -- a self-hosted status/monitoring page, so you find out a service is down from a dashboard instead of from a family member.
• A secrets/password manager you actually use (Vaultwarden is the common self-hosted Bitwarden-compatible choice) -- homelabs accumulate admin passwords fast, and reusing one everywhere is a real risk once you're exposing anything at all to your network, let alone the internet.

Verify it works

• You've joined at least one community relevant to something you're actually running or planning to build
• You've browsed Awesome-Selfhosted (or Awesome-Sysadmin) for at least one category relevant to your setup
• You've bookmarked the official docs for at least one tool you're currently running
• You can name, even loosely, what a reverse proxy and an uptime monitor would each solve for you once your homelab grows past one or two services

Troubleshooting

This guide is a reference, not a build, so there's nothing here to troubleshoot in the usual sense -- if a specific linked resource has moved or gone offline, search for its current name directly; software and communities in this space change hosts and names more often than established enterprise tools do.

Next steps

Pick one project from this section that matches something you actually want running, and build it. This reference list is meant to be revisited as you go, not read once and closed.

Sources

Community and project links current as of this guide's last update date above; verify against the linked source directly, since community-run resources can move or change over time in a way official vendor docs usually don't.