Question
Letsencrypt Shows Expired, Renewal Fails, Litespeed Wordpress Droplet
- Posted on March 4, 2020
- Ubuntu 18.04
Asked by internetjason
My domain shows an expired cert even though Certbot says renewal is not needed. I tried a dry run renewal and got the following error. I’m not sure what to do. This is on DigitalOcean having used the Litespeed Wordpress Droplet.
Attempting to renew cert (www.thinkliz.com) from /etc/letsencrypt/renewal/www.thinkliz.com.conf produced an unexpected error: urn:ietf:params:acme:error:malformed :: The request message was malformed :: Method not allowed. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.thinkliz.com/fullchain.pem (failure)
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Hello, @internetjason
It seems like your SSL Certificate has expired. Could you please post the versions of your installed Certbot packages? In particular python3-acme.
If it is not at 0.31.0-2, perhaps try to forcefully upgrade it:
And then try to renew the certificate again and execute the –dry-run as well.
Let me know how it goes.
Regards, Alex
I had a similar, maybe not related, issue recently with our litespeed server. Went in to perform a renewal and it wasn’t needed. However, on my browser it was telling me the connection wasn’t secure and the cert had an older date.
This was resolved when I performed a graceful restart on the litespeed panel. This has happened before. Not sure if there is some kind of cache issue.