My domain is: cashcrunchloan.firstcalgary.com AND cashcrunchloan.chinookfinancial.com I ran this command: sudo certbot renew --dry-run It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log -------------------------------------------------------------------------------…

So Certbot actually is version 0.22.2. The python-certbot-apache package is version 0.25.0… however, it’s a simple transitional dummy package, and it doesn’t depend on a specific version of the current Apache plugin package, python3-certbot-apache. You can check “dpkg -l python3-certbot-apache” bu…

Could not decode 'status' when performing a renew dry run

Help

cpu June 20, 2018, 7:24pm 2

Hi @byates,

This looks like the result of a recent change to the ACMEv2 staging environment adding the "ready" status: ACMEv2 Order "ready" Status

@byates What version of Certbot are you using? I believe the required fix is in version 0.25.0

How to Update Certbot on Ubuntu 18.04.1

Deserialization error: Status not recognized

Topic		Replies	Views
Deserialization error: Could not decode 'status' ('ready') Help	4	2863	November 26, 2018
Error sudo certbot renew --dry-run: Could not decode 'status' ('ready') Help	5	3056	August 13, 2018
Can't renew by certbot: Could not decode 'status' (u'ready') Help	11	5533	July 29, 2018
Dry run works, but real renew has all renewal attempts fail with: "produced an unexpected error: [Errno 17] File exists: '/etc/letsencrypt/archive/mydomain.com/privkey3.pem" Help	11	3273	December 2, 2019
Certbot renew --dry-run fails Help	6	4997	February 16, 2020

Could not decode 'status' when performing a renew dry run

Related topics