Rocketchat group calls are also using Jitsi, so including that would be a big plus for us.

Rocketchat group calls are also using Jitsi, so including that would be a big plus for us.

We are attempting to use a wildcard cert for one of our domains.

I attempted using the key and cert as provided (no ca chain), which the UI accepted, but then on restart, all subdomains were using self-signed certs.

After working around HSTS, I was able to get back into the system and switch back to Lets Encrypt.

Next, I tried including the ca bundle in the cert file. When I did it the wrong way around (ca certs before the wildcard cert), the UI reported an error. When done the other way (as per NGINX documentation), the UI accepted the cert. However, all subdomains were using a self-signed cert again.

The renewcerts log showed an error along the lines of "null certificate, falling back to self-signed". Unfortunately, I didn't capture the logs at the time, and the available history doesn't go back that far.

I've tried various certificate inspection tools, that have reported the certificate as valid. This is the same provider we use for providing wildcard certs for non-Cloudron domains, that we SSL-terminate with NGINX, which is why I thought to try the ca-bundle inclusion.

Can anyone provide any insight into why this would have failed in this manner?

We have a SoGo setup from before Cloudron supported multiple domains, and SMTP supported authenticating with just the account name.

Since the full email address is now a requirement, SoGo has been failing to send emails.

I fixed/worked around this by adding the following setting to the /app/data/sogo.conf file (instead of migrating all the data to a new SoGo instance).

SOGoForceExternalLoginWithEmail = YES;

Thought I'd share this in case anyone else runs into the same issue.