Update to new Certbot version installation


#1

My domain is: picklikeapro.com

I ran this command:
sudo apt-get update
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:certbot/certbot
sudo apt-get update
sudo apt-get install python-certbot-nginx

It produced this output:

My web server is (include version):nginx/1.10.3 (Ubuntu)

The operating system my web server runs on is (include version):ubuntu 16.04

My hosting provider, if applicable, is: Digitalocean

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

I am trying to update the package of the certbot version from 0.22.0 to 0.26.1 but to no avail. It says it’s the latest but when I run the version command, it says the same.


#2

Hi,

What’s your python version?

Thank you


#3

Hi,

Thanks for the reply.

Python 2.7.12

And if I do “sudo certbot renew --dry-run”, I get this long error where most noticeable one is this-

Attempting to renew cert (picklikeapro.com) from /etc/letsencrypt/renewal/picklikeapro.com.conf produced an unexpected error: Deserialization error: Could not decode ‘status’ (‘ready’): Deserialization error: Status not recognized. Skipping.

What is wrong here please?

Full error report-

Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/crud.madcoderz.com.conf

Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator nginx, Installer nginx
Renewing an existing certificate
Attempting to renew cert (crud.madcoderz.com) from /etc/letsencrypt/renewal/crud .madcoderz.com.conf produced an unexpected error: Deserialization error: Could n ot decode ‘status’ (‘ready’): Deserialization error: Status not recognized. Skip ping.


Processing /etc/letsencrypt/renewal/picklikeapro.com.conf

Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator nginx, Installer nginx
Renewing an existing certificate
Attempting to renew cert (picklikeapro.com) from /etc/letsencrypt/renewal/picklikeapro.com.conf produced an unexpected error: Deserialization error: Could not decode ‘status’ (‘ready’): Deserialization error: Status not recognized. Skipping.


Processing /etc/letsencrypt/renewal/pos.madcoderz.com.conf

Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator nginx, Installer nginx
Renewing an existing certificate
Attempting to renew cert (pos.madcoderz.com) from /etc/letsencrypt/renewal/pos.madcoderz.com.conf produced an unexpected error: Deserialization error: Could not decode ‘status’ (‘ready’): Deserialization error: Status not recognized. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/crud.madcoderz.com/fullchain.pem (failure)
/etc/letsencrypt/live/picklikeapro.com/fullchain.pem (failure)
/etc/letsencrypt/live/pos.madcoderz.com/fullchain.pem (failure)

** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/crud.madcoderz.com/fullchain.pem (failure)
/etc/letsencrypt/live/picklikeapro.com/fullchain.pem (failure)
/etc/letsencrypt/live/pos.madcoderz.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

3 renew failure(s), 0 parse failure(s)

Thank you so much


#4

What happens if you run “sudo apt full-upgrade”?


#5

Wow! Certbot upgraded to the new version and the errors are gone…worked like a charm!!!

Thanks a lot man!

BTW, could you please explain why the errors happened? What does the error actually mean if you please?

The error was mainly -
Deserialization error: Could not decode ‘status’ (‘ready’): Deserialization error: Status not recognized.

Thanks again. You saved my day.


#6

Hi @rpmcmurphy

“ready” is a new status, active since 2018-07-05.

Your client has to support this status. Too old - no support, no certificate.


#7

So the problem was with Certbot version as far as I can understand. And I am after this for long hours trying to find problem with my nginx configuration.

Thank you


#8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.