@teleclimber You could use Let's Encrypt to get a wildcard certificate for your local domain (or subdomain) through DNS authentication (it is the recommended best-practice to assign a real domain/sub-domain for internal use, to avoid any conflicts).
An alternative (that I deployed for my own usage) is using @tailscale which will provide this "internal" domain, generate the certificates, and as a bonus allow me to access my "internal" services from everywhere
Conversation
Notices
-
Embed this notice
Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 09-Nov-2023 17:55:24 JST Renaud Chaput -
Embed this notice
Olivier Forget (teleclimber@social.tchncs.de)'s status on Thursday, 09-Nov-2023 17:55:26 JST Olivier Forget #TLS in a private home network: is there anything being worked on to make this easier? The options seem to be:
- get a valid cert using a purchased domain name and use it internally
- become your own root CA and install root certs on each deviceBoth have significant downsides. But if you do neither you don't get that sweet sweet HTTPS that is needed for so many web features (webcam access, PWA, etc..)
Is any work being done to help improve this situation?
-
Embed this notice