Hi Giacomo,
well, somehow you get it done. But the user expanse is (sorry) terrible. The UI is not free of interpretation and offers enough possibilities to be misunderstood.
Many use cases require manual intervention…
you do it by hand since all files are packed in a tar.gz.
use the command line:
…or are not well documented.
- delete a name from the current certificate, then request it again
Especially the use case “explicit certificates for individual vhosts”, is not documented anywhere.
The deletion is hidden in the documentation of the base system (old).
It is not without reason that I needed so much support; and that is why I have been using SSL certificates for years. Initially created and managed manually, then under Plesk. But the UI makes it difficult to transfer know-how because it is not clear what consequences a certain procedure has bow. which procedure has to be practiced to get an expected result.
The feature request does not mean “offer any possibility to manage certificates”, it is about optimization, especially user experience.
For example, I would prefer to have a function on each vhost to create dedicated LE certificates.
Of course, you can also take the standpoint that I was particularly clumsy here. But I don’t really want to put on this shoe.