Selfhosted

60093 readers

951 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

SSL certificates for things inside the lab (lemmy.zip)

submitted 3 months ago by gblues@lemmy.zip to c/selfhosted@lemmy.world

25 comments fedilink hide all child comments

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

[–] Decq@lemmy.world 2 points 3 months ago* (last edited 3 months ago)

Let's encrypt doesn't have to be accessible from the web, it accesses the web itself. It's a subtly difference i guess, but you don't need port forwarding or anything. Of course if your jellyfin/immich service is completely blocked from going out on the internet then it still won't work.

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

I don't think that's true. But Let's encrypt does need to verify the domain name. If it's just a domain you made up in your LAN that is an issue yes. But I have no experience with that though.

You could use self-signed certificates, they are free. but you would need to add custom trusted CA to all the user devices manually. I've never done this myself so no clue how troublesome this really is.

What I do is have a reverse proxy that requests a wildcard certificate (e.g '*.example.com') with Let's encrypt. And then route all my services through the reverse proxy with subdomains. You can get free domains with duckdns.org or others.