Selfhosted

60093 readers

830 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 30 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

Best reverse proxy with ACME to run in docker (lemmy.world)

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

38 comments fedilink hide all child comments

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

[–] JRaccoon@discuss.tchncs.de 21 points 3 months ago (2 children)

I use Caddy and it's great. ACME is very easy to configure, as is everything else. I haven't tried running it in a container tho but they have official images published so it should work without issues.

[–] mereo@piefed.ca 8 points 3 months ago (1 children)

I don't think running Caddy in a container is needed. All my apps are docker images and Caddy is a system app. I treated as an important OS app.

[–] JRaccoon@discuss.tchncs.de 2 points 3 months ago

Agreed

[–] motruck@lemmy.zip 4 points 3 months ago* (last edited 3 months ago)

I run it in a container without problems. All you have you do is bind it to port 80 and 443. I prefer the container to running it directly within the host OS for ease of portability.

Also strongly recommend building it with support for DNS based validation. Using DNS validation you can have multiple instances running across the different servers you have to easily switch to or provide better local routing. For example please. I run one caddy frontend on a VPS that routes my traffic most of the time, but when I'm at home my DNS points me at a caddy instance that is running on my server on my home network avoiding the path of out to the internet and back home. Using http based validation would require me to sync certs around.