this post was submitted on 11 Aug 2023
20 points (95.5% liked)

Selfhosted

40218 readers
1037 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
 

I was hoping to get some help from you all, since I assume there are a good number of people here selfhosting their own instance of Lemmy. There doesn't appear to be a search bar for per community searching, so I thought I'd post my question in case anyone else has a similar one. I've created my own Lemmy instance running in Docker based on the dev's provided documentation. Used their example docker-compose.yml file and others, and just customized the needed options. I've got everything working except one important part, TLS/SSL certs. I'm not familiar with nginx at all, but it seems like I simply need to map another volume from local:container for the cert, however when I've mapped certbot/conf/:/etc/nginx/ssl/ and restart all the containers, this doesn't enable HTTPS.

I've read a couple different places online that talk about adding CertBot as a service etc, however none of these were specially for Lemmy. So I wasn't sure this would work given the extra config file for nginx. Any advice on how you all got this to work would be appreciated! Thank you in advance :)

Edit: thanks for all the advice everyone! Sounds like I’ll be going the reverse proxy route, either with caddy or npm. Both seem simple enough to implement. Thanks again, and happy Friday!

you are viewing a single comment's thread
view the rest of the comments
[–] DrJenkem@lemmy.blugatch.tube 4 points 1 year ago (1 children)

Nginx-proxy-manager makes dealing with certs easier imo. You can either have it setup to double proxy (point to the nginx you already have running) or replace the existing nginx (you'll have to copy the config into nginx-proxy-manager ui).

[–] walden@sub.wetshaving.social 2 points 1 year ago (1 children)

I like NPM a lot. Nginx on its own was confusing to me. NPM is fast to configure and works really well.

[–] Aux@lemmy.world 0 points 1 year ago

Standalone nginx is confusing because it was designed to be as fast as possible. Developers have sacrificed everything for this goal.