What still needs to be done to get this released?
Let's Encrypt's change went live yesterday and this bug can be easily
reproduced. Probably the easiest way to do this is to set up an Ubuntu
18.04 server that is reachable on port 80 with nothing currently
listening to the port and a public domain pointing to the server. After
that, install certbot and run:
certbot certonly --agree-tos --domain <your domain>
--register-unsafely-without-email --staging --standalone
certbot renew --force-renewal
Certbot should fail with output including:
Attempting to renew cert (<your domain>) from
/etc/letsencrypt/renewal/<your domain>.conf produced an unexpected
error: Deserialization error: Could not decode 'status' ('ready'):
Deserialization error: Status not recognized. Skipping.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777205
Title:
python-acme to start crashing on June 19th
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1777205/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
