Stop typing IP addresses: set up local DNS and SSL for your homelab

Support the channel: Use Unraid: https://linkbarry.cc/Unraid The full guide: https://projects.benjaminspowell.com/... The ultimate FOSS directory: https://ourlocalhost.com AdGuard Home: https://ourlocalhost.com/?q=adguard%2... Nginx Proxy Manager: https://ourlocalhost.com/?q=nginx%20p... ------------- Still opening apps in your homelab with raw IP addresses and random ports? That works for a while, but it gets messy fast. In this video I set up AdGuard Home and Nginx Proxy Manager on Ubuntu Server so local services can use proper internal domains like convert.home.arpa, route cleanly across the network, and load over HTTPS with a local wildcard certificate. This is useful if you want a cleaner home network, easier access to self-hosted apps, better control over local DNS, and a setup that scales properly as you add more services. Instead of memorising 192.168.x.x:3000, you can give each app a proper name and put a reverse proxy in front of it, which makes the whole stack feel far more usable and far less improvised. In this setup I use AdGuard Home for local DNS rewrites, Nginx Proxy Manager for reverse proxying, and a self-signed wildcard certificate for *.home.arpa so internal services can run on HTTPS without needing to expose anything publicly. It is a good approach for homelab users who want internal domains, local SSL, VLAN-aware DNS control, and a more polished way to reach services on their LAN. The full written guide includes the exact terminal commands, Docker Compose files, certificate generation, AdGuard settings, and proxy configuration used in the video, so you can follow the same working setup end to end without piecing it together from scattered docs.