Could not decode 'status' ('ready'): Deserialization error: Status not recognized

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain

I ran this command:
certbot certonly --manual --preferred-challenges dns -d smtp.com1.tld
then this:certbot certonly --manual --preferred-challenges dns --cert-name smtp.dom1.tld -d mail.dom2.tld,mail.dom3.tld
then:revoked and deleted smtp.dom1.tld (revoked because I realized later that I should have included smtp in the -d option)
certbot certonly --manual --preferred-challenges dns -d smtp.com1.tld

which then produced this output:josepy.errors.DeserializationError: Deserialization error: Could not decode ‘status’ (‘ready’): Deserialization error: Status not recognized

The operating system my web server runs on is (include version):Linux HOSTNAME 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30) x86_64 GNU/Linux

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):certbot 0.23.0

Hi @mohitgodiya

that's a simple problem.

This status ready is ~~ new (ok, last year).


your certbot is too old to support that status.

1 Like

Hello @JuergenAuer

Thanks a ton for the quick reply.
I will attempt to update my certbot. Hopefully it does not break my existing certs.
I found the same reply in suggestion in a couple of different posts but was not sure if it applied to my case. Since I clearly messed up my own certs.

Hello @JuergenAuer:
suggestion worked as expected. I now have my cert with all the SANs I need.

Do you by any chance know what is the limit (if any) on the number of SANs we can have for a cert? and don’t really say if there is a limit on SANs.

1 Like

That's impossible. If you have created a certificate, you can use it.

The problem is max. the next renew.

Happy to read that.

You can create one certificate with max. 100 domain names. That should be enough.

Most of the limits are domain specific - max. 5 identical certificates / week, max. 50 certificates per week per domain.

So if you have 5 - 10 subdomains, the limits shouldn't be a problem.

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