[BlueOnyx:20128] Re: BlueOnyx 5209R LE Certbot 0.9.1 error

Michael Stauber mstauber at blueonyx.it
Mon Oct 10 14:25:22 -05 2016


Hi Roger,

> I was requesting a new certificate from Let's Encrypt today, which
> triggered a certbot-auto upgrade to version 0.9.1.
> The subsequent request failed with the following error:
> “An unexpected error occurred: Bug in pythondialog: expected an empty
> output from u'infobox', but got: u'Error opening terminal:
> unknown.\n'Please see the logfile 'certbot.log' for more details.“
> 
> A quick fix was to edit
> “/usr/sausalito/handlers/base/ssl/le_install.pl” and add the “--text”
> switch to the letsencrypt-auto command.
> 
> Certbot command line option:
> -t, --text Use the text output instead of the curses UI.

Thank you very much for reporting the problem *and* the fix. That's
really appreciated!

I just looked at in and you're right: The Let's Encrypt guys committed a
cardinal sin and broke expected behaviour. Previously the -t (or --text)
switch wasn't needed. Now we need it to get the expected behaviour. \o/

I'm rolling up an update now which will be published to the YUM
repositories within the next two hours. I went one step further, though:

I not only added --text, but also --no-self-upgrade to all our
letsencrypt-auto calls. I'm getting sick and tired of their upgrades
breaking expected behaviour and we'll use the current 0.91 version until
it no longer works. Then I'll publish an update that either replaces the
ACME client with something else, or we upgrade it again to a working
version.

For shits and giggles I upgraded certbot-auto as well (we don't use it).
And the latest version of that actually *demands* that the EPEL YUM
repository is activated *all* the time. It bitches if it isn't enabled.
Sorry, Let's Encrypt guys: That straw breaks the camel's back. ;-)

-- 
With best regards

Michael Stauber



More information about the Blueonyx mailing list