-
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
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.
HatBeard
Was making decent inroads on my setup then proxmox decided it was going to deny random requests to http calls to it's gui so it was constantly showing lost connection spinners and not loading anything. thought i'd completely fucked it when trying to reinstall certain parts from apt it stopped loading altogether but somehow managed to get it up and running long enough to rescue a full back of my HA config i'd spent a full day on. was feeling pretty bummed i'd lost all my efforts of the last few days though.
changed tact and thought I'd install pi hole on a rpi and maybe try to tidy up the local networking dns so i knew my proxmox setup was seeing the right thing and resolving requests properly. got as far as a fully working pihole and unbound setup running on dietpi and hooked up to my router dhcp as it's dns. then felt really uneasy about how it would behave if the pi ever went down. ended up switching out to nextdns.io instead and had it up and running in about 10 minutes with working local dns record resolution for my upcoming local services (plex etc).
having felt like another day was wasted I just wiped my nuc completely, reinstalled proxmox (twice, the first time I managed to type the same wrong password twice in the installer and got locked out).
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.