Thanks for the plugin. I am running OMV on port 81, put a nginx (using nginx plugins) on port 80 just for webroot validation and redirecting all other things to https://. My https nginx do reverse proxy for every other service (transmission, omv on port 81, etc). In this way I did not need to mass with internal services ssl configuration, good enough.
I had an error that took me a while to figure out. I removed, by accident, the certificate created by plugin using webgui/certificates page. After this letsencrypt plugin start fail because it cannot find the UUID of certificate object in OMV system. There is no way to configure this item through webgui and letsencrypt plugin has no fall-back-create-again-solution. If a complete remove and reinstall resulted in the same error. I manage to solve it by editing config.xml and removing letsencrypt config by hand. After reinstalling plugin I could generate certificate again.
Suggestion: implement a bailout plan in case the configured uuid is missing, in my opinion create a new on would be the best way to do. This should be done even if letsencrypt returns "no renew necessary" because if someone, like me, is dumb enough to delete certificate by mistake, a renew would restore it in place.
Suggestion 2: Implement some way to generate independent certificates. Lets assume someone host two completely different domains, one for OMV and other under omv-nginx plugin for serve a different site. This person will not want to use combined certificate for those two domains but separated certificates to completely separate both domains (imagine if this second domain is, someday, moved to another server, the combined cert does not make sense anymore).
Thanks for the great work!
att,
Benito
