Home/Notes/What a plant nursery needs to know about certificate renewals
What a plant nursery needs to know about certificate renewals
27 Dec 2024
How a plant nursery deals with certificate renewals — and what usually goes wrong.
The problem: a 2 MB photo in a 320-pixel slot. The certificate chain breaks for a plant nursery.
We rotate API keys for certificate renewals annually. a plant nursery did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
When a plant nursery moved hosts, the outage was not the new box — it was a 2 MB photo in a 320-pixel slot. We keep TTL short the week of a move, then raise it once everything is stable.
DNS propagation is not instant, but it is not magic either. We explained to a plant nursery that the TTL on the old certificate renewals record was 86 400 seconds — twenty-four hours.
For a plant nursery, the boring path won: HTTPS, a backup that we have restored once on purpose, and a calendar reminder for certificate renewals.
Complexity is the enemy of uptime. a plant nursery had three layers of proxy in front of a site that gets two hundred visits a day. We replaced it with a static page and correct certificate renewals.
If you only touch certificate renewals once a year, a dashboard is extra risk. Files, a mailbox you read, and a person who still answers will outlast any SaaS control panel.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com