> When you use the tailscale serve command with the HTTPS protocol, Tailscale automatically provisions a TLS certificate for your unique tailnet DNS name.
So is the certificate not valid? The 'Limitations' section doesn't mention anything about TLS either:
Becoming more politically active has been a massive source of community for me. And if community is already endangered (which isn't something I disagree with, by the way - so many people are inadequately supported), that's all the more reason we should find and build it.
A KDE dev mentioned on a podcast that issues related to Debian Stable get closed automatically on their bug tracker because fixes don't get backported :/
My wife was complaining about Windows issues so I ended up installing Fedora with KDE on her laptop. I would have preferred Debian but using Testing (as suggested by the dev) doesn't some ideal.
Debian Testing isn't really unstable - the dev wasn't exaggerating. But I'd also suggest Kubuntu (you can remove snap and all of its packages, and install Firefox and Thunderbird .deb's from the Mozilla repo)
You're thinking of Unstable (Sid). It's also not like Arch or Tumbleweed because it gets locked down during release freeze and then gets a ton of updates all at once.
> tailscale serve --service=svc:web-server --https=443 127.0.0.1:8080
> http://web-server.<tailnet-name>.ts.net:443/ > |-- proxy http://127.0.0.1:8080
> When you use the tailscale serve command with the HTTPS protocol, Tailscale automatically provisions a TLS certificate for your unique tailnet DNS name.
So is the certificate not valid? The 'Limitations' section doesn't mention anything about TLS either:
https://tailscale.com/docs/features/tailscale-services#limit...
reply