I love my homelab, and the more I tune things the more satisfaction I have. I tolerated the “Your connection is not private” for my self-signed SSL certs on my services for way too long.

I just setup NGINX Proxy Manager as a LXC on my Proxmox Server and pointed a subdomain I own to the server. Now I have custom domains for each service along with valid SSL Certificates. It’s all local without exposing anything to the outside world. It’s very satisfying. I tried explaining what I was doing to my GF but she could care less ¯\_(ツ)_/¯

Followed this video from Wolfgang’s Channel YouTube (great channel btw), the first minute does a better job explaining the setup. I always thought I would have to setup a local CA which is more work than I was interested in, but this approach was much simpler (and free!).

  • RedSquirrelFtw@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I recently did the same! I was using a bunch of individual .loc domains for all my servers and I recently moved to using a sub domain off a real domain that I own. It feels more professional because that’s how my work does it for their network. So everything is servername.int.mydomain.com. I setup Lets encrypt on my web server and I have a local rsync script that just grabs the cert off the web server. I didn’t do all of my servers yet but did the more important ones. Of course those only resolve locally since the records are local only. int.mydomain.com resolves externally as a wild card and just goes to a common page that does nothing but it allows for Lets Encrypt validation to work.

    Firefox has this annoying thing where it warns you about unsecured passwords in forms and I was really getting irritated by that on my local dev server because it does like a drop down thing that gets in the way of the rest of the form.

    For now I’m just specifying each sub domain to LE, but I eventually want to setup the zone as dynamic and do a wildcard, which requires to do a txt record or something… it’s a bit more involved so didn’t look at it yet.

    I also discovered the DHCP option “search domain”. Seen it before but never really knew what it was. Well you can specify your subdomain in there so that on any workstation getting DHCP you can time servername and it will auto complete the .sub.domain.tld part. I guess this is how windows 98 Netbios used to work. I just never really put the two and two together.