Posts by robster
-
-
... 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
-
-
-
-
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"
}
]
}
}
-
-
hmm, it says:
https://i.imgur.com/zsdKtfA.png
But I definitely have an SSL cert. Checking my terminal on the server I get:
$ certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: [redacted]
Domains: [redacted]
Expiry Date: 2022-04-20 06:00:47+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/redacted/fullchain.pem
Private Key Path: /etc/letsencrypt/live/redacted/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
@TeWuEs did it recently in ths thread RE: Can not login with host.domain but can with IP address maybe he can give detailed instructions.
Thank you.
I went there, started asking, looked over my interface and... guess what?
I was entering the data into SSH not SSL. There are two tabs.So now my keys are accepted, in the system... and I still have a broken lock on my address bar. sigh.
Oh well, one step at a time!
I definitely have a valid letsencrypt cert. I also have it imported in the OMV interface. I just have to keep plugging away.Thanks again everyone!
-
-
Yup
I noted that. However, it's a virtual device but in the end it all worked out. Learning every step of the way.
Thank you
-
-
-
As OMV requires two (or more) hard drives, I had to create a VPS but I also needed a second drive. Vultr allows you to create another drive using Block Storage and link it to the VPS. So the VPS sees a literal other physical drive. It works well. However, I simply installed to the wrong drive.
-
There is! Thank you. I found the import in the dropdown.
I pasted the results of cat privkey.pem into the box.
However, there is one called public key in the omv interface. Which file's contents should I paste into that? fullchain maybe? Well, I tried that and it says invalid format. I'm not sure. It's really not clear in the docs.
Thanks again for this.
-
For example, in the OMV docs I found this statement RE letsencrypt:
LetsEncrypt
Lets Encrypt certificates can be imported directly, just locate your
/etc/letsencrypt/live/<mydomain.com>/fullchain,privkey.pem
files and copy their contents in their respective field. No need to convert.So I looked on the filesystem, and found the following:
cert.pem
chain.pem
fullchain.pem
privkey.pem
README
So I'm just not sure what to do. I am not finding the docs clear based on that paragraph.
-
I found out my mistake. I was installing omv to the Block Storage, not the server. So the public ip was not seeing omv, only the debian server. I did again, installed to the server and the block storage is now a storage drive for omv. So it's working now
-
-
Thank you for this. However I am a bit new to SSL certs.
As a note, this is a public facing machine, it's not behind my modem. I've got a server on Vultr and can access via subdomain.domain.com if that makes any difference.
I've gone and created a ssl cert using the certbot command :
certbot --nginx --redirect -d subdomain.domain.com -d subdomain.domain.com -m email@address.com --agree-tos
However, how does that let me use it in omv? I am sorry I don't understand what you mean by "copy the new cert on top of the old one and restart nginx in your script" in regard to what I've done.
Thank you
-
Hi all,
I've logged in via SSH and run the following command:
certbot --nginx --redirect -d subdomain.domain.com -d subdomain.domain.com -m email@address.com --agree-tos
This gave me a certificate which is great.
However, I note theres a certificate section in the Secure Connection area in the Web Administration area. I drop down that option and nothing is there.
How can I ensure OMV is using my certificate?
Thank you