Hello Yummiweb,
I understand your concerns regarding the changes in certificate management after the Core 3.6.0 update. This change is a small step back before a bigger leap forward!
We are gradually introducing new features (see, for example, User portal, unprotected access from the outside - #14 by davidep), and the current UI still needs refinement. As we approach the end of milestone 8.4, I’ll provide more details in the official announcement and release notes.
With Core 3.6.0 and Traefik 3.0.0, ACME-issued TLS certificates are no longer listed under the “TLS Certificates” page. This change works around a bug that caused duplicate listings. Additionally, in some installations, the page became cluttered and difficult to read due to an excessive number of items. While the current situation isn’t ideal, it’s a temporary trade-off, and we plan to improve it in an upcoming UI update.
TLS certificates required by applications and obtained via ACME always have a single name—other application names are not revealed.
On the other hand, when you request a certificate from the “TLS Certificates” page, you are now configuring the main (first) and any additional (SAN) names for a single certificate, similar to how NS7 handled it. Applications that currently follow this approach include Mail, Ejabberd, and NethVoice Proxy. Given their use cases, the impact of revealing their hostnames in a single certificate is minimal.