Over the past few days when I’ve logged in to my MIAB I’ve seen
The TLS (SSL) certificate has a problem: The certificate has expired or is not yet valid. It is valid from 2018-07-12 19:16:27 to 2018-10-10 19:16:27.
This is for the box.mydomain.com certificate. I started to panic yesterday. Looking around here I found people who said I just needed to run sudo mailinabox and it would get a new certificate after asking me to agree to the certbot TOS. That didn’t happen. Digging a bit further I found a suggestion to run ssl_certificates.py. This produces an error
Traceback (most recent call last):
File “/root/mailinabox/management/./ssl_certificates.py”, line 660, in
File “/root/mailinabox/management/./ssl_certificates.py”, line 372, in provision_certificates_cmdline
status = provision_certificates(env, limit_domains=domains)
File “/root/mailinabox/management/./ssl_certificates.py”, line 348, in provision_certificates
File “/root/mailinabox/management/./ssl_certificates.py”, line 458, in post_install_func
if cert and os.readlink(system_ssl_certificate) != cert[‘certificate’]:
OSError: [Errno 22] Invalid argument: ‘/home/user-data/ssl/ssl_certificate.pem’
As you’ll observe this certificate has expired and my MIAB has now become semi-unusable. I’ve tried running certbot manually but I can’t figure the exact command to recreate the cert in a way that MIAB can use it - it does create it in the certbot/live folder.
As I mentioned, I’ve found things like this
If you recently upgraded (to 0.28) Let’s Encrypt changed something on their end which is causing the MiaB install script to skip their request to accept their ToS. Typically rerunning sudo mailinabox will fix this.
But that doesn’t happen. The MIAB installer runs without an error though.
Anyone have any suggestions on why this cert didn’t renew and/or how I can renew it?