Internet Of Things / IoT / Connected Home / Smart Houses

You are reading a single comment by @HatBeard and its replies. Click here to read the full conversation.

•

Howard in reply to @HatBeard

I then did some tinkering to turn on my namecheap.com api access and then hooked my proxmox install up to letsencrypt via namecheap dns resolution and now in tandem with the nextdns record for my nuc I have a fully working ssl cert running on a local ip resolving my subdomain from an actual dns entry for a real domain which feels like finally a decent step in the right direction.

Wow...the future is so simple

•

HatBeard in reply to @Howard

well I mean it will now auto-renew my ssl cert and reapply for free indefinitely without me touching a thing on my server or at my domain registrar again.

9/10 home networks have no need for a real domain to be used for the dns. most of the time they'll use .local and live with browsers throwing a shit-fit every time you load the page and haven't opted out of the certificate warning but it is a pain in the arse if you're using a lot of stuff locally.

they're both convenience changes but already they've made the rest of the setup much smoother so far.

•

jellybaby in reply to @HatBeard

if you're using a lot of stuff locally

I installed my own CA for that reason.
•

NotThamesWater in reply to @HatBeard

I didn't think that you could auto-renew with letsencrypt - Don't you need to provide a new DNS TXT record each time to show that you actually own the domain?

Or is that the bit that you have set up automagically

About

Avatar for HatBeard @HatBeard started