Confconsole - Let's Encrypt/Dehydrated - Handle errors better; give better info

[JedMeister]

It has been suggested that when an error occurs getting a Let's Encrypt certificate via Confconsole, the exact error is not always (perhaps never?) displayed in the UI.

Also the message "FATAL: dehydrated exited with a non-zero exit code" and a note to "check the log file" (without even noting where the log file is) is not that helpful... On reflection, it actually reminds me a bit of a Microsoft Windows error message!

[JedMeister]

This is perhaps somewhat related to #1498?!

[l-arnold]

This is happening right now in both New TKL Odoo 16.1 and slightly used TKL Odoo 16.1.
Let's Encrypt was working a week ago on the hub but this is not a Hub Install. Just did a fresh install and the same error listed "exited with a non-zero exit code."
On the slightly used install that has SSL in Apache I get a more verbose albeit similar non-functional situation (even trying to run when Apache is stopped)

(perhaps related to version changes happening now???)

Perhaps also related: Confconsole is very slow to start in slightly used version.
Re Confconsole I seem to have made the mistake of running "apt-get upgrade" yesterday after "apt-get update".
Confconsole is taking up to 5 minutes to appear.

[JedMeister]

@l-arnold - when you got the "exited with a non-zero exit code." error message, did you work out the issue?

Re slow starting, I'm not at all sure what might have caused that?! I assume that you are starting it from the commandline, with confconsole right? Then it takes a while to actually appear? Is that what you mean?

[l-arnold]

It seems the "exited with a non-zero exit code." happens after I have previously applied a SSL cert externally to Apache, then try to generate a new one with Let's Encrypt. (Had similar experience in TKL 14, 15 and 16 versions)

Separately, the CONFCONSOLE is very slow to start when envoked from SSH. It does come but seems to take 2 minuites or so to show itself.

I likely will do a new build, then try a TKL-BAM restore. Best if I do that that I block any SSL Restoration.

I will note that after this I did pull some Lets Encrypt certificates over to this server as I needed to get some certs in place. That gave me a 3 month window to work out long term and I am about 2 weeks into that now.