“The certificate renewed successfully,” says the support reply. Yet your staff still see a warning when they open the invoice portal. How can both things be true?
The missing step may be installation. Obtaining a new certificate and having the customer-facing service use it are not the same event. A useful way to understand certificate maintenance is to follow the whole journey, from issuing the replacement to checking what the customer receives. The certificate-management standard describes renewal as obtaining a new certificate, not extending the old file’s dates. 6
To follow the problem, imagine staff opening portal.example.com. Their browser, the program displaying the website, asks a server for the portal. A server is the computer system that answers. Before sending account information through a protected connection, the browser checks the certificate the server presents. The certificate is a signed digital document that links a website name to public information used to check the server’s identity. A separate private key stays secret and lets the server prove that the document belongs with the system answering. 5 18
The document is not your company’s login password. It is part of the service’s ability to establish an accepted connection. If the browser cannot accept it, staff may meet a warning before they even reach the normal account sign-in. A certificate fault can therefore interrupt daily work even when the invoice records themselves are still on the server. The warning does not mean those records have vanished. 5
A certificate comes with an end date
A web certificate helps a browser verify the identity of the service it reaches. It has a validity interval: a time before which it is not yet valid and a time after which its validity has ended. These limits are part of the information checked when the certificate is assessed. They are not merely a reminder in the operator’s calendar. 5
Think of a time-limited pass. Ordering a replacement pass is useful, but leaving it in an office drawer will not help the person who still presents the old one at the entrance. Similarly, a new certificate must reach the right service, and that service must actually begin presenting it. Renewal success is an intermediate step, not the customer’s final experience. 6
Certificates do not all last the same length of time. For publicly trusted web-server certificates covered by the CA/Browser Forum rules, those issued from 15 March 2026 until before 15 March 2027 may last at most 200 days. An issuer can choose a shorter lifetime; older certificates and other certificate types follow their applicable rules. 20
The business lesson is not to memorise that number forever. It is to arrange maintenance that follows the actual certificate and the rules that apply to it. If the normal renewal fails, there should still be time for someone to notice and repair the problem before customers lose access.
Renewal means getting a new certificate
When issuing a certificate, its issuer — the certificate authority — checks the applicant’s right to obtain a certificate for the name. Let’s Encrypt describes proving control of the domain, then requesting a certificate containing the appropriate public key. Renewal repeats the issuance process. It does not open the old certificate and edit its expiry date. 4 6
Software can do much of this repetitive work. One widely used method is ACME, a standard for automated certificate management. It lets software deal with tasks such as requesting certificates and responding to the authority’s checks. Automation is useful precisely because certificates need continuing attention rather than a one-off purchase. 6
Follow one renewal from beginning to end. The management program requests a replacement for portal.example.com. The issuer may ask it to demonstrate control by placing specified data where the issuer can check them. After the check and successful issuance, the program downloads the new certificate. At this point, the replacement has been obtained; the portal may still be using the old certificate.
The operator’s setup must then make the portal use the new certificate with the matching private key. Finally, the operator checks the intended connection to see what visitors are actually offered. The steps therefore answer different questions: was control demonstrated, was a document issued, was it installed, and is the live service using it? 4 6
Suppose the download succeeds but the replacement remains in the management program’s working folder. The portal continues presenting the old document. An alert based only on obtaining the replacement can say “success” while the customer’s browser still complains. Alternatively, the request can fail while the old certificate remains valid, so the portal looks normal for the moment. These two cases explain why waiting for users to complain is a poor way to discover a renewal problem. The operator needs to notice failed steps before the old validity period ends. 6
But the surrounding setup still matters. For example, a renewal method may rely on adding an entry to the domain’s published settings. If the account that can make that change is no longer available, the process may fail. This is why a website can look healthy immediately after a supplier change while a future renewal dependency remains unresolved. 4 6
The domain can also publish a rule limiting which certificate authorities may issue certificates for it. This rule is called CAA and is stored in DNS, the Internet directory for domain information. When changing issuer, the operator may need to update that permission. A later CAA change does not cancel certificates already issued. 19
Check what customers actually receive
Return to the support reply at the start. A successful renewal message could mean the new certificate has been obtained. If the live service still presents the old one, customers can still have a problem. The next question is therefore not “Did the task run?” but “What certificate does the intended service present now?” 6
My recommendation is to check both the renewal process and the resulting connection. The first tells the operator whether the certificate request succeeded. The second checks whether the customer-facing service uses the expected certificate. If several independently configured systems serve the same business function, the operator should explain how they are covered rather than assuming one successful check represents all of them.
Alerts also need a person who can act. An expiry warning sent only to a former agency, or to an employee on leave, leaves the business with a notification but no response. For a small company, it is enough to start with a clear support contact and a backup contact. You should not have to know the encryption settings to know whom to call.
During a supplier handover, ask about the next renewal, not only the current certificate. Can the incoming operator complete the domain check, obtain the replacement and make the service use it? Discuss the process without asking anyone to circulate private keys or passwords in ordinary email.
Sometimes replacement cannot wait for expiry
Expiry is the planned end of a certificate’s validity. Revocation is different: the issuer marks a certificate as no longer to be trusted before that scheduled end. A reason could be exposure of the private key, the secret information used to prove the server’s identity. Let’s Encrypt describes revocation for certificates that are no longer safe to use. 7
If the private key may have escaped, simply obtaining another certificate is not a complete response. The operator needs to address the exposed key and the access problem, replace affected material and arrange revocation where appropriate. Otherwise the reason for the emergency remains. 7
Revocation is not a promise that every browser and program everywhere will reject the old certificate at the same instant. The issuer publishes revocation information; client behaviour also matters. The operator must deal with the incident rather than treating a revocation request as a universal off switch. 7
For your business, start with one important service: the portal staff actually use, not whichever company website is easiest to find. Ask who maintains its certificate, who hears about a failed renewal and whether the service was checked after the last replacement. Those answers tell you more about continuity than a certificate installed once and forgotten.
Sources
[4] Let’s Encrypt — How It Works
[5] IETF RFC 5280 — X.509 Certificates and Revocation
[7] Let’s Encrypt — Revoking Certificates
[19] IETF RFC 8659 — DNS Certification Authority Authorization
[20] CA/Browser Forum — TLS Baseline Requirements, section 6.3.2
[18] IETF RFC 9846 — TLS 1.3 (July 2026; obsoletes RFC 8446)