this post was submitted on 28 Feb 2026
38 points (97.5% liked)

Selfhosted

60426 readers
209 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I've been self hosting traditionally in debian, but I would like to be able to add services easier using docker. As such, I'm looking to move to a container based architecture.

One place I struggle is that I can't seem to find a good container where the default image supports ACME to support Let's encrypt for automatic cert renewal.

For Nginx, I would have you build my container. HAproxy ACME support seems to be a shell script.

Any suggestions?

you are viewing a single comment's thread
view the rest of the comments
[–] twelvety@fedia.io 1 points 4 months ago

I use:

  • Apache with Letsencrypt client for single host reverse proxies or those with more complex needs. Not the easiest but when you understand it, it's fine. Lightweight, solid and very flexible.
  • NPM, either service or docker, where there's a lot of proxies on one host. Very simple, very reliable, baked in authentication.
  • Traefik, when building or deploying services, especially with docker swarm. Tags make it very smooth once you've got things set up and in your workflow.

All are good choices, but each has a specialism that make it a little bit better than the others.