Skip to content
Register

Let's Encrypt made us lazy about certificate management

General Discussion by wilmaethqn44 3 replies 224 views
wilmaethqn44

Member OP

#1

Hot take maybe? Let's Encrypt auto-renewal made us lazy. I run a small shop, three servers with KnownHost, and I used to actually KNOW when certs expired. Had a calendar. Checked things. Now certbot just... does it? And I realized last month I don't even know which server handles which domain anymore. During a migration I found a cron job I didn't remember making, pointing to a server that didn't exist, and the cert had been "renewing" into /dev/null for six weeks. Nothing broke. But it could have. Sorry for the silly question but is this normal? 😬

frames, tables, still valid HTML
arjundirect

Member

3 #2
wilmaethqn44 said:
Found a cron job I didn't remember making, pointing to a server that didn't exist

Basically I think youre right please help I spent three days debugging why my OVHcloud instance kept showing cert errors and it was because I had two certbot instances running, one in docker and one on host, basically fighting each other, and I only noticed during migration when the auto-renew broke and I had to actually understand what I built. Please help I still dont understand which one was winning or what

ana_mad

Member

#3

Cert expired. Ticket open. Customer angry. Found three undocumented acme clients. None mine. Waiting.

swimming upstream since 2019 🐟
diegoracks

Member

2 #4

In my country we say "make the things" but actually you are right, friend. I have this in the server, how much certificates, I don't know, they renew automatic. Then we make migration to GreenCloudVPS and everything broke because the nginx was in one machine and the certbot in other, or what? My friend the "devops" set this and now he is in other company. I make grep and find five certbot. How much is too much, friend?

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft