I’m brand new to certificate management so please forgive me if my issues and questions make me sound ignorant.
I have set up a personal home server using FreeNAS which is a port of FreeBSD, i believe. The build is FreeNAS-9.3-STABLE-201412090314.
I currently have 7 application jails successfully running. one of these have https set up already, but I’ll be honest and say that I just followed some “cookbook” instructions to set up the openssl in the jail. The jail app with SSL is ownCloud – my family’s personal cloud storage solution. The ownCloud install was done using NGINX, PHP-FPM, and MySQL per this walkthrough: https://forums.freenas.org/index.php?threads/how-to-owncloud-using-nginx-php-fpm-and-mysql.17786/
I currently pay DynDNS.org for a domain that is always synced to my router’s IP. Let’s call it “CostonDomain.net” (for example).
Currently I can go to https: //CostonDomain.net:12808 to access my FreeNAS server’s web GUI, and I can go to https: //CostonDomain.net/owncloud to access my ownCloud server. This works because I configured my router to forward port 443 to the ownCloud server’s IP on my home network and I have port 12808 being forwarded to the FreeNAS WebGUI IP with FreeNAS configured to “listen” for https traffic on that same port.
What I’d like to do is to install the same domain verification certificate from Let’sEncrypt on both of these so whenever I try to access either the FreeNAS GUI or my ownCloud server from outside my home network using https: //CostonDomain.net… I won’t get the browser’s domain not valid error screen.
Is this possible? If so, How do I go about obtaining the cerificate? I’m hoping someone reading this is familiar with FreeNAS systems and jails.
I’ve already tried multiple times to follow the tutorials at Let’sEncrypt, but I am doing something wrong.
Again, please forgive my ignorance.