To cover the root domain you need to include community.skunkhenry.com as an alternative name in the cert. I'm not sure how the SSL cert was created but I don't see an issuer in the cert details on chrome, so to include a SAN it should just take some config changes on the openssl config file to include the root domain on wherever the cert is being generated.
You will have to re-generate a cert and then replace it on the cluster router there are some SOP's in the OSD ops-sop repo for replacing router certs I can point you to. |
|
