I’ve been downloading SSL certificates from my domain provider, using cat to join them together to make the fullchain.pem, uploading them to the server, and myself adding a 90 day calendar reminder. Every time I did this I’d think I should find out about this Certbot thing.

Well, I finally got around to it, and it was one of those jobs which turns out to be so easy you wish you’d done it ages ago.

The install was simple (I’m using nginx/ubuntu).

It scans up your server conf files to see which sites are being served, asks you a couple of questions, obtains the Let’s Encrypt certificate for them, installs it, updates your conf files to use it, and sets up a cron job to check if it’s time to renew the certificate, which it will also do auto-magically.

I was so pleased with it I made a donation to the EFF for it, then I started to think about how amazingly useful Let’s Encrypt is, and gave them one too. It’s just a really good time to be in this hobby.

I highly recommend Certbot. If you’ve been putting this off, or only just hearing about it, make some time for it.

62 points
*
Deleted by creator
permalink
report
reply
23 points

Or traefik

permalink
report
parent
reply
9 points

traefik worked for me once. Then I tried to use it again in a different and I didn’t manage to get it to run. Caddy is much simpler. Traefik is more powerful but just for Let’s Encrypt I would go with Caddy.

permalink
report
parent
reply
3 points

I took a look at Traefik once and the complexity scared me away. Caddy is my cup of tea with one simple config file.

permalink
report
parent
reply
0 points

@clb92 @Appoxo …but traefik’s autoconfigure from labels on your services in the compose file is so nice.

permalink
report
parent
reply
3 points

Or swag ;)

permalink
report
parent
reply
2 points

Or Nginx Proxy Manager.

permalink
report
parent
reply
1 point

So many tools. Yet not enough time.

permalink
report
parent
reply
30 points

You know what, thanks for making this post. I have used Letsencrypt and Certbot for years now, i’d never have thought about donating, but since you said that I just made a donation.

permalink
report
reply
7 points

Good on you. For anyone else inspired, you can support Certbot here, and Let’s Encrypt here.

I promise I don’t work for them - I was just struck by how phenomenally handy they are.

permalink
report
parent
reply
27 points

Certbot is great when using Nginx (or Apache2), but if you can use a different engine. Its worthwhile checking out Caddy!

permalink
report
reply
24 points
permalink
report
reply
9 points

This is what I use because fuck snap. I used certbot to do wild card certs but once they went to snap I quit.

permalink
report
parent
reply
5 points

This seems like free hate as you can use certbot without snap without any problems. Imagine stopping using Firefox because of the same reason for example

permalink
report
parent
reply
5 points
*

On Debian you can apt install certbot and it’s just a regular Debian package with Python files inside. Are you on Ubuntu? I know they’ve been pushing snaps for a while.

permalink
report
parent
reply
1 point

The certbot authors tried really hard at one point to make snap the only available distribution mechanism for their application and for some time the version that Fedora packaged would display some weird deprecation warning and urge you to use the snap version.

permalink
report
parent
reply
3 points

That’s exactly the same reason I dropped certbot, haha

permalink
report
parent
reply
1 point

Fun fact: It’s in Arch’s repos.

permalink
report
parent
reply
1 point

If you don’t like snap, maybe you should try another distro instead (I went to fedora because I was annnoyed of snaps).

permalink
report
parent
reply
3 points

I also use acme.sh. It has worked great for me and was dead simple to use. Super flexible on what it can do from just renewing the certs to web server integration. Love the simple to use hooks available too.

permalink
report
parent
reply
1 point

Certbot has hooks too.

permalink
report
parent
reply
17 points
*

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

Fewer Letters More Letters
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
IP Internet Protocol
LXC Linux Containers
PiHole Network-wide ad-blocker (DNS sinkhole)
SSL Secure Sockets Layer, for transparent encryption
TLS Transport Layer Security, supersedes SSL
VPS Virtual Private Server (opposed to shared hosting)
nginx Popular HTTP server

7 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

[Thread #120 for this sub, first seen 8th Sep 2023, 16:25] [FAQ] [Full list] [Contact] [Source code]

permalink
report
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.5K

    Posts

  • 78K

    Comments