Cert errors after upate

[ecourt]

after last upgrade, I’m getting these emails daily from MiaB
Any thoughts on what’s going on?

Traceback (most recent call last): File “/root/mailinabox/management/ssl_certificates.py”, line 682, in provision_certificates_cmdline() File “/root/mailinabox/management/ssl_certificates.py”, line 393, in provision_certificates_cmdline status = provision_certificates(env, limit_domains=domains) File “/root/mailinabox/management/ssl_certificates.py”, line 369, in provision_certificates ret.extend(post_install_func(env)) File “/root/mailinabox/management/ssl_certificates.py”, line 479, 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’

[KiekerJan]

Look at the output of ls -l /home/user-data/ssl/ what files are there?

[ecourt]

6 .pem files, and a lets_encrypt directory

[KiekerJan]

One of them should be called ssl_certificate.pem, it should be symlink to another (real) pem file. Are both present and what are their access rights and file ownerships?

[ecourt]

It is there, but it’s not a symlink.

-rw-r–r-- 1 root root 3602 Feb 23 19:37 ssl_certificate.pem

[ecourt]

Made a copy of the ssl_certificate.pem file, – re ran the install and it recreated…
are there any other sym links in that user-data directory?
I had to recover from a backup of that directory a couple months ago, and I suspect my backup only followed the sym-link, and did not copy it.

[KiekerJan]

What you can try: backup the ssl_certificate.pem, then create the symlink manually. There should be a box.domain file you can link it to. Then rerun the provisioning.

The error you see is probably because MiaB expects a symlink, but the file is not a symlink. No clue why a real file is created on reinstall, it should be a symlink.