Following a recent post on how I use Tailscale and NextDNS to manage my home network
Tailscale Part 3 - How I run my Home NetworkI’ve written quite a bit about Tailscale and its features. In this post, I’ll be covering how I’ve utilised the technology in
Hard to believe you used to have to pay for a TLS certificate. I use Let's Encrypt with cert-manager on my kubernetes cluster and it still amazes me how SSL just happens. Even just using certbot makes the job extremely simple.
For cert-manager to work you need to have the ingress controller port (or I guess another port) exposed publicly? Or it supports DNS verification? I thought about doing this, but I am essentially having my cluster fully in a private network which I connect with wireguard from outside, but maybe I should reconsider?
I am keen to know a little bit more about your setup
As a side note, how do people handle HTTPS with private networks (VPN or local) these days? I typically just stick to HTTP, but it would be nice to get rid of the warnings/lock (and I use HTTPS-only mode and firefox seems to require a fresh exception for every port).
Doing what the OP (same result, just different software) or I posted and assigning certificates to secure your local services means you can avoid the HTTPS warning that major browsers will pop up on an unsecure (HTTP) connection. Instead of going to an internal dns name without a certificate or direct to the ip....you assign a wildcard certificate to a domain name you've setup on your local dns. You then access that service via the HTTPS protected Domain name, with no warning.
I also use this for my stuff. I don't have too open any inbound ports at all or worry about the fact that I'm on a dynamic IP, I just access things over my local IPs / hostnames as though I'm on my home LAN.
I can't open the link right now cause it seems to have gotten the hug of death, but if they didn't mention it check out Caddy. It handles the certificates all automatically. All you have to do is set up the DNS record and then point Caddy at your internal service and it handles the rest.
I unfortunately agree :( I wanted to use LE, but I really didn't want a bunch of extra infrastructure. I ended up ponying up for a domain cert. It was expensive, but it's really easy for all of my k8s Ingress/IngressRoute/HTTPProxy objects to use it.
Is there a lets-encrypt alternative that doesn't require you to pay for a domain? I'd like to use a local domain like myservice.home rather than myservice.domain.com. I currently have Caddy auto generate certificates for my services but it's a pain as some devices hate the self-signed certificate.
There might be a better way, but I have used free duckdns domain to generate lets encrypt cert. Im not even sure if that worked only because I had duckdns running on the same host
Self signed certificates. I have my services with a .local domain, created a 10year certificate. The only painful thing is that you have to import your CA into all of your devices