this post was submitted on 04 Oct 2023
0 points (NaN% liked)

Selfhosted

40313 readers
185 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.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hey everyone,

Just a quick question, let's encrypt, what is it and how can I take advantage of its services?

For a bit of background I'm trying to setup KanIDM and the need for a ca certificate is needed, I was told to use let's encrypt to create it.

Just looking for knowledge.

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] vector_zero@lemmy.world 0 points 1 year ago (1 children)

I'm going to cast another vote for a reverse proxy, such as NginxProxyManager. It's really easy to set everything up, and they're usually very easy to run in Docker/Podman.

One thing to note: if you end up with a domain with mandatory HSTS, you'll have to use DNS-based certificate generation rather than HTTP based, since unencrypted HTTP is blocked (chicken/egg problem to get HTTPS working). It's not hard, but you have to be aware of that limitation.

[–] pete_the_cat@lemmy.world 1 points 1 year ago

As someone that used Nginx for close to decade, Caddy is about 10x simpler with the same features. It takes a bit to wrap your head around if you're used to coming from an "old-school" webserver and proxy like Apache or Nginx though. One of the greatest things about Caddy is that it does SSL by default, so there's no need to have stanzas in each section saying "listen on 80 and 443, but if you get a connection on 80 redirect it to 443" and another one saying "enable SSL for this (sub)domain". Creating a reverse proxy in Caddy literally takes three lines and consists of FQDN { reverse_proxy internal-endpoint-name:portNumber }