this post was submitted on 16 Mar 2026
68 points (97.2% liked)

Selfhosted

57595 readers
1946 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hello everyone. Need some opinions here. Does it worth all the trouble to make things like jellyfin and immich run with HTTPS for services that are only accesible in the LAN? I ask it 'cause, as far as I know, there is no way to put a valid certificate like let's encrypt for a service that is not accessible from the net and I don't plan to buy a certificate for myself. But I have some trouble with the rest of my family having issue with their browsers complaining about the lack of https every time a browser is updated. So, what would be the best solution?

you are viewing a single comment's thread
view the rest of the comments
[–] disobey2623@lemmy.dbzer0.com 5 points 2 hours ago* (last edited 2 hours ago)

Many people talking about using subdomains, but that's only really a thing if you actually have a domain. Just last year the domain .internal was reserved for internal use, so that's what I've set up all my domains to use. E.g. https://pihole.internal/, https://proxmox.internal/.

To make this work I use pihole's local dns records to rewrite any *.internal domain to point to my reverse proxy Caddy's ip.

As for the certificates, I created my own CA, which I install on all my and my family's devices. Then, for each new url I set up, I create a new certificate and sign it with my CA certificate, then have my reverse proxy serve it.

This all sounds like a lot of work, and it is, but using OPNsense for both reverse proxy and certificates makes it well integrated and certificates are trivial to renew. With that said, if you have your own domain, go the let's encrypt subdomain route instead imo. It saves you a lot of manual labor with setting up your CA on every device you own and creating new certificates for each site.