Issues With HTTPS Certificate

[Jason Roberts]

Hi all, great to be part of this, however am new to FreeNAS never used it before untill 3 days ago, i installed and installed a few other bits without any issues, however i have been trying all night to sort out this HTTPS certivicate, each time i generate one in my browser it comes up with invalid certificate, any help would be great thanks

 

[danb35]

A lot more detail would help (off the top of my head, the exact version of FreeNAS, what you're doing to generate a certificate, and exactly what the error message says), but any self-generated certificate is likely give errors.

 

[Jason Roberts]

Hi, the FreeNAS version am using is 9.3, to generate a certificate am first going in to CAs (create internal Ca) then into certificates next to it on the right ans creating internal certificate, the error messages them self's come from chrome,

 

[danb35]

If you click on the red lock icon in Chrome, it will give you more information about the error. But most likely it's as I noted above--self-signed certificates are going to give you error messages, because browsers don't know and trust the CAs (i.e., you) who issued them. You should be able to resolve them by configuring Chrome to trust the certificate. Here's one of the more recent links a quick Google search found: https://www.accuweaver.com/2014/09/19/make-chrome-accept-a-self-signed-certificate-on-osx/

Note that I can't vouch for that link; it's just one that came up on Google. Searching for "chrome trust self-signed certificate" brings up others.

 

[Jason Roberts]

Here are the images of the error, as i say am new to this but in time i guess ill learn, lol also i would like to install owncloud but i guess because i got this issue i wouldent know if its secure or not... thanks for taking the time buddy :)

 

[danb35]

There are lots of pieces to the puzzle that is HTTPS. Here are some of them, but I'll probably miss some:

• The certificate needs to come from a trusted source. By default, your browser won't trust a self-signed cert. You can make it trust the cert, at least most of the time. Google (or search engine of your choice) is your friend here.
• A certificate is issued for a hostname, not an IP address. The hostname you're accessing must match (one of) the hostname(s) on the certificate. Since an IP address doesn't match a hostname, browsing to an IP address will give you a certificate error.
• The certificate has a set time for which it's valid. If you try to access before or after that time period, you'll get an error.

Now, OwnCloud is going to be a completely separate issue--it will be installed in a jail, which will run its own web server, and needs its own TLS certificate created, installed, and configured. Your TLS settings on the FreeNAS web GUI will have no effect on owncloud.

 

[Jason Roberts]

Ok, thanks i think ill give it up as a bad job lol, cheers for your guidance