I have certbot installed on the server, how can I get it to work in the OMV GUI / ensure OMV is using it?

  • I can't help it and I know you're right, I still can't help it.


    Definitely did that. Have my URL correct.

    Interestingly, now I've added the certbot to OMV, I can't even view the http version. I'm locked out so to speak :)

  • Open the browser, in the browser open the development tools (F12 usually).

    open the networks tab.

    enter http://my_server into the address bar and hit enter.


    Show me what is in the network tab.



    or (on your windows machine):


    curl -vvv http://name_of_my_server

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Thanks for your continued interest and suggestions.


    I'm on Debian 10 linux btw in case that helps (on my machine and of course the server).


    The network tab shows:


    {

    "Request Headers (651 B)": {

    "headers": [

    {

    "name": "Accept",

    "value": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8"

    },

    {

    "name": "Accept-Encoding",

    "value": "gzip, deflate, br"

    },

    {

    "name": "Accept-Language",

    "value": "en-US,en;q=0.5"

    },

    {

    "name": "Connection",

    "value": "keep-alive"

    },

    {

    "name": "Cookie",

    "value": "X-OPENMEDIAVAULT-SESSIONID=jgfe22ca15icmaiabbs6a1bhgp; X-OPENMEDIAVAULT-LOGIN-%242y%2410%24GATO9j4Dm7dktYDEuowhguyu0rIYHxMsGMfqeGxWLtFoOGgEykWYO=What+does+a+mirror+look+at%3F"

    },

    {

    "name": "DNT",

    "value": "1"

    },

    {

    "name": "Host",

    "value": "omv.redactedDomain.com"

    },

    {

    "name": "Sec-Fetch-Dest",

    "value": "document"

    },

    {

    "name": "Sec-Fetch-Mode",

    "value": "navigate"

    },

    {

    "name": "Sec-Fetch-Site",

    "value": "none"

    },

    {

    "name": "Sec-Fetch-User",

    "value": "?1"

    },

    {

    "name": "Sec-GPC",

    "value": "1"

    },

    {

    "name": "Upgrade-Insecure-Requests",

    "value": "1"

    },

    {

    "name": "User-Agent",

    "value": "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0"

    }

    ]

    }

    }

  • 301 means moved, which is a redirect to https.


    As a first aid measure, you can check if omv-firstaid will allow you to set it back to http.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • OK I did a full re-format, re-installed OMV.


    Installed letsencrypt with the certbot.


    Imported the certificate into omv.


    Now, I get this! Moving forward. So there's a cert that's recognised, however, it is the error as shown at the bottom of this screen shot.


  • however, it is the error as shown at the bottom of this screen shot.

    As I see it, that is not an error.

    On the contrary, it states that the connection is beeing encrypted

  • ... and I have no idea why. I have re-loaded using the base URL and it works! I wonder what the hell that was all about?


    I really want to thank you for all your help. I'll be doing up a doc for future people to work through to run omv on vultr with letsencrypt. So they can have a front facing system, if they so want to take the risk.


    thanks again, it's so very much appreciated

  • macom

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

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