Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
But as you reported, your site is still using an older (expired) certificate, instead of one of the newer ones that exist.
Since you got these using a control panel, it seems like the panel itself is installed or configured incorrectly, because it seems to be unable to deploy the certificates that it obtains. Do you have support for this control panel from anyone, like the hosting provider or the control panel developer? It seems like you’ve done the right thing but your hosting environment has a configuration error of some sort that’s someone else’s responsibility to address.
Appreciate your quick reply. As you mentioned, I had the hosting provider (IONOS Team) to check this and they said a hung nginx process was preventing implementation of LE renewal and it had been killed; however, after performing the killing action when the plesk support team wanted to include the “www” in the certificate by renewing the LE cert from Domains -> azimuthacademy.com -> Let’s Encrypt -> Renew they hit the following error:
The “Certificates per Registered Domain” rate limit has been exceeded for azimuthacademy.com. Let’s Encrypt allows no more than 50 certificates to be issued per registered domain, per week.
They want me to wait a week & see. Is there any suggestion how I proceed from your side?
Also When I browse www.azimuthacademy.com, I can see the certificate date now renewed to 3 months but still privacy error is occurring.
So you have 5 identical certificates with both domain names (www and non-www), that's the
We also have a Duplicate Certificate limit of 5 certificates per week. A certificate is considered a duplicate of an earlier certificate if they contain the exact same set of hostnames, ignoring capitalization and ordering of hostnames.
Limit. But there are not 50 certificates.
And there is another problem you (or your hosting company) should fix: