Remember it is a wildcard cert. It goes to multiple servers. Just happens I made it for the untangle but it is the same format OMV wanted. You need to find the name to the name of the cert that you imported by web ui. Then rename it to that.
Sorry for the confusion.
If you make it idiot proof, somebody will build a better idiot.
I tested your method and my method again tonight and they both worked.
after import the cert and keys into OMV via the Import menu, go to /etc/ssl/private and /etc/ssl/certs, to find the openmediavault-unique-key....
Next, use cp to copy the files from /etc/letsencrypt/live/example.com/ to /etc/ssl/private and /etc/ssl/certs appropriately.
I have Let's Encrypt certs, but I don't know how to import them into OMV in order to enable SSL. I'm sure this is super simple. I'm just a complete noob with certs.
I can't use the letsencrypt Docker because port 80 is blocked and RCN wanted $19/month (plus activation fee!) to unblock it. I used acme.sh's DNS API mode to successfully get certs from Let's Encrypt. I believe I need to import the certs into OMV, but I don't know how to do this.
I've got a ".cer" cert, a ".key" cert key, and a ".cer" intermediate CA cert. The OMV documentation on certificates says that the certs can be imported directly: openmediavault.readthedocs.io/…general/certificates.html
I very much don't want to manually cat the cert files and copy & paste the contents into the OMV UI. How can I script the import of the Let's Encrypt certs, given that their location will be static?