Lets Encrypt plugin - What web root?

  • I have OMV 4 running with a ton of services running in Docker... And I don't really know what to put in the plugin for the webroot. I tried "/var/www/openmediavault" but that failed the challenges. I'm running Plex, HASSIO, qBittorrent, Radarr and several others. Any help would be appreciated.


    Also, as a suggestion, maybe a future version of the plugin could run it's own challenge without needing to ask for a web root and then as an option a user can specify the webroot if they are trying to use it for something specific.


    Update - also I should mention that I have nothing running on port 80 just for the Let's Encrypt plugin to run.

  • Yes the port is forwarded. Let's Encrypt also works great in couple of addons in HASSIO, so I know that my port forwarding works. Nothing on that side of things has changed.


    I'm trying to get the plugin working so that I can easily use the same cert over the entire system easily. I can declare it as a volume in other Docker images. I'm sure that I could do that with a Docker image too, but this is how I'm experimenting with things at the moment. I'm trying to solve the broken cert warning in the browser for all my different services and I'd like for it to just work. Instead I'm seeing an old cert in some windows and applying on cert across the whole system, starting at the root with OMV seems like a reasonable idea.

  • I'm going to upgrade OMV and install HASSIO, so I'm going to be in the same situation.
    Isn't possible to use the DuckDNS plugin (with Let's Encrypt included) and "pass" (manually? cron?) the file from HASSIO to main OMV?
    If I understand, you want to generate the cert with plugin and pass it to HASSIO docker image ... is it ok? But in OMV 5 (the version I'm going to install) Let's Encrypt is only by docker, not by plugin ...

  • I'm running HASSIO

    Just a question: Do you run HASSIO or Home Assistant?
    I'm asking because, if i understand, installing via docker (docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /PATH_TO_YOUR_CONFIG:/config --net=host homeassistant/home-assistant:stable) install Home Assistant and not HASSIO. HASSIO should be installed using this (curl -sL https://raw.githubusercontent.…/master/hassio_install.sh). Is it correct? I prefer installing HASSIO but the second way of installation seems to be worst ...

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!