Nice!
I was actually googling for a status of certbot on epel release and did not manage to find anything.
That link is great.
Gives all the info one needs.
I am seeing this same issue on my Ubuntu server which according to my apt is up to date.
dpkg -l certbot python-certbot python3-certbot
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±=============================================-===========================-===========================-===============================================================================================
ii certbot 0.23.0-1 all automatically configure HTTPS using Let’s Encrypt
ii python3-certbot 0.23.0-1 all main library for certbot
dpkg-query: no packages found matching python-certbot
This is the result of my attempt to renew the certificate using
sudo /usr/bin/certbot renew --dry-run
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Attempting to renew cert (public..oh.us) from /etc/letsencrypt/renewal/public..oh.us.conf produced an unexpected error: Deserialization error: Could not decode ‘status’ (‘ready’): Deserialization error: Status not recognized. Skipping.
I see that there was a number of updates for the apache server. Is there an update that is stuck in limbo for the Ubuntu distro?
mnorfhoff
I tried your suggestion. Initially, it did not help. But I decided to try to uninstall the old packages and reinstall. With the new packages install the issue was resolved.
Thanks,