I do have domain I can use. But how will it work in my local network? Will I point on domain to “192.168…” ?? Will that work if I just set to local IP address? That would eliminate issues of trusting certs, but that will mean it will work for me locally or perhaps for other people too, locally, if IP is the same?
For my ‘private’ services that I don’t want public (plex.domain.com, nas.domain.com, etc), I don’t publish DNS records for those with the registrar. Instead I have them set up in NPM with letsencrypt certs, and local DNS that my router points to.
I don’t have clodufare or amazon accounts. Domain hosted at register.com. All videos/FAQs I found point to cloudfare. Is that mandatory and will free account suffice?
My advice for just about every tinkerer and homelabber.
Spend ten bucks on a real domain name, then use a free Cloudflare account to manage dns for the domain. It makes life so, so easy with ssl, npm, letsencrypt, acme, all that stuff. I use one of my public domains as my lan domain.
Already did. I had public domain, just didn’t think how to use it “inside”. Now it makes sense. All actually works, and I don’t mind for cloudflare to be controller, like I said, domain is paid for but wasn’t used for anything.
Still don’t understand what cloudfare actually does But SSL works. When it auto-renews I will officially declare it “magic”
Yes cloudflare gives you an api key you can plug in so you get real, valid for everyone ssl certs. It just has to control dns for your domain. It does not manage my Lan hosts, I do that, but I use my api key to perform dns validation like magic.