If you desire to have your URL's include the "www" subdomain, you must place that in all of the variables noted in the tutorial for domains. I excluded the "www" on my panel certificate set up on purpose once I understood all of this vaguely, but feel if only for nostalgia sake my domains should include the "www" subdomain after the https:// and before your FQDN. (This little thing also makes the address look nicer/more traditional as the address in most browsers will default to displaying "www.your.domain.com" which is smaller and cleaner looking than having the https:// in there on its own.)
Without including the "www" in the tutorial varribles, https://panel.yourdomin.com will not issue you a warning when you go to the aforementioned address, but if you try and reach the domain with https://www.panel.yourdomain.com or simply:
you will get the "broken certificate" warning.
Personally I did NOT use the "www" subdomain for my SENTORA panel, but DID include it for any website domains SENTORA is hosting.
@TGates, is this mentioned in any of the tutorials yet? I know I have it right for the domain tutorial, but did not actually try it for the panel (including the www...) If not, might it be something to include? Tiny things like this, for me waste countless hours of my time over something so simple that I had merely overlooked it. -> just as I had overlooked which file needed the Listen 443 commented out ( 443) and separate installation of mod_ssl in CentOS for SENTORA which was my own oversite, I should have come to that conclusion quickly, but sometimes I can not see the forest for the trees in front of me.
lol What do I say now? "Don't ask me how I know this..." (Because I make lots of mistakes!)
Without including the "www" in the tutorial varribles, https://panel.yourdomin.com will not issue you a warning when you go to the aforementioned address, but if you try and reach the domain with https://www.panel.yourdomain.com or simply:
Code:
www.panel.yourdomain.comyou will get the "broken certificate" warning.
Personally I did NOT use the "www" subdomain for my SENTORA panel, but DID include it for any website domains SENTORA is hosting.
@TGates, is this mentioned in any of the tutorials yet? I know I have it right for the domain tutorial, but did not actually try it for the panel (including the www...) If not, might it be something to include? Tiny things like this, for me waste countless hours of my time over something so simple that I had merely overlooked it. -> just as I had overlooked which file needed the Listen 443 commented out ( 443) and separate installation of mod_ssl in CentOS for SENTORA which was my own oversite, I should have come to that conclusion quickly, but sometimes I can not see the forest for the trees in front of me.
lol What do I say now? "Don't ask me how I know this..." (Because I make lots of mistakes!)
Everyone makes mistakes, but to truly screw up it takes the root password!
