Hello, I wan’t to ask if anyone knows of a good alternative for certbot for acquiring ssl certificates for nginx.

Certbot isn’t good anymore for me since I started using crowdsec with nginx bouncer that uses lua block’s inside nginx config that cerbot can’t parse, making it not work anymore.

I use nginx because it’s the one I know the best and for my use case work’s the best. ( Hosting both program’s directly on metal and docker container’s )

0 points

New Lemmy Post: Alternative to certbot for acquiring ssl certificates to use with nginx. (https://lemmy.world/post/11122593)
Tagging: #SelfHosted

(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)

I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md

permalink
report
reply
6 points
permalink
report
reply
4 points

NixOS uses this, works well for me.

permalink
report
parent
reply
3 points

What CA are you getting your certificates from?

If Let’s Encrypt, have you checked their alternative methods to certbot?

permalink
report
reply
2 points

Yea I’m using let’s encrypt. Juet wanted to hear opinions from people who are probably more experienced than me.

permalink
report
parent
reply
2 points

I’d say any project that’s decently maintained and satisfies your use case is probably good enough. I found this that from the sound of it fits your use case: https://github.com/fffonion/lua-resty-acme

permalink
report
parent
reply
5 points
*

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
CA (SSL) Certificate Authority
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
SSL Secure Sockets Layer, for transparent encryption
nginx Popular HTTP server

3 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.

[Thread #452 for this sub, first seen 24th Jan 2024, 12:25] [FAQ] [Full list] [Contact] [Source code]

permalink
report
reply
12 points

if you are open to learn something new: Caddy webserver has a dead simple config, fetches tls certs by default for you and works with crowdsec too

permalink
report
reply
7 points

Caddy is fantastic, incredibly easy to configure and just works out of the box beautifully.

permalink
report
parent
reply

Do you have it on host or container. I’m thinking abour switching to caddy on my host and replacing nginx with it but just wan’t to hear your experience with it.

permalink
report
parent
reply
2 points

I run it in its own separate VM. Normally I use containers for everything, but Caddy being the part that’s most on the outside of my network, as it were, I wanted to separate off.

permalink
report
parent
reply
1 point
*

I’m open to using sothing like caddy or traefic, but my issue is I have a mix of packages hosted directly on system and in docker container’s and as such need to proxy them all.

That’s why I’m not using caddy or traefic.

Edit: rn my mix consists of about 16 diff containeraized stuff and another 4-5 not containerized stuff.

Edit2: Just now realized that they can be used on the host system’s also. Would you recommend traefic or caddy?

permalink
report
parent
reply
2 points

If all was containerised, I’d recommend traefik for its impeccable container integration, but for a mix of bare metal and container services I’d go with Caddy.

permalink
report
parent
reply
2 points
*

I’m using Caddy (sometimes in a container or most of the time as system package) as reverse proxy mostly for containers
I try to minimize non-container services but they work well with Caddy too

Traefik is a tad more complex (still nowhere near Apache2 levels though) but scales more easily espcially if you only run containers and start/stop them programatically

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 4.7K

    Monthly active users

  • 3.2K

    Posts

  • 71K

    Comments