this post was submitted on 10 Mar 2024
17 points (90.5% liked)

Technology

55387 readers
27 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
top 12 comments
sorted by: hot top controversial new old
[–] timbuck2themoon@sh.itjust.works 5 points 3 months ago (1 children)

I stopped using certbot when they made it nothing but a snap.

Lego, acme.sh, and tools like caddy, traefik, cert-manager can easily replaced it afaiac.

[–] jlh@lemmy.jlh.name 2 points 3 months ago (1 children)

Those look some really cool options! I might end up using one of these for my environment.

[–] naticus@lemmy.world 2 points 3 months ago* (last edited 3 months ago)

Can confirm that acme.sh is a great option. Way better support of many DNS APIs than Certbot, including easier setup of wildcard certificates. Personally moved to this when Certbot's ability to do RFC2136 (dynamic DNS method that many DNS servers support) was seriously lacking, and never looked back.

[–] notannpc@lemmy.world 2 points 3 months ago

I’ve used traefik for 7 years at this point and the only time I had to think about certificates was when I blocked my servers running traefik from making DNS calls needed for the cert generation.

I’ve got 6 domains now all with certs managed by traefik. Highly recommend checking it out, especially if you’re running most things in docker.

[–] lemann@lemmy.dbzer0.com 1 points 3 months ago

I use certbot on only a single one of my oldest projects that has been going for almost a decade.

For everything else I use acme.sh because it works so well and integrates with a ton of DNS providers. The one time I had an issue, it was already fixed in a PR, so I just checked out that fixed version and used it for renewals until it was merged in.

[–] pztrn@bin.pztrn.name 1 points 3 months ago

Using Caddy for couple of years already at home, yet using certbot at job, because of requirements to use nginx as balancer.

[–] jlh@lemmy.jlh.name 1 points 3 months ago

cert-manager works really well.

[–] JoeKrogan@lemmy.world 0 points 3 months ago (1 children)

No. Not everyone uses traefik or caddy

[–] BenPranklin@lemmy.world 1 points 3 months ago* (last edited 3 months ago)

Yeah man, that's the point of the article. Its asking the question "should everyone who isnt using them already move to them". Its not saying everyone already does.

[–] abhibeckert@lemmy.world -1 points 3 months ago (1 children)

Certbot is so problematic we still pay for most of our certificates because it’s more reliable.

I’m not sure if Caddy/Traefik is the answer but it’s clear the work should be handed over to a team with a proper focus on reliability.

[–] pastermil@sh.itjust.works 3 points 3 months ago (1 children)

Can you elaborate on this reliability issue?

[–] abhibeckert@lemmy.world 1 points 3 months ago* (last edited 3 months ago)

Certbot is supposed to automatically renew certificates. It doesn't do that reliably in my experience.

We use it on non-critical systems and every few months I need to go in and fix things... that never happens with traditional certificates - those are setup and forget.

As for the exact problems, I don't think we've ever had the same problem twice. It's always a once off thing but it's still an hour of wasted time each and every time. If it happened on a proper production system it'd be a lot more than an hour, since whatever change is made would need a full gamut of testing / reporting / etc.