OK, I have properly set up a Let'sEncrypt certificate on my subdomain, panel.example.com - which is fine.
I want to use example.com on 443 using SSL, but due to the subdomain procedure for panel.example.com, when running the procedure for the domain example.com, it retains the cert. for panel.example.com and gives me the normal non matching URL error in the browsers.
I think I saw something about this here before, but cannot find it now. I am wondering, I don't think Let'sEncrypt has set up for wildcards, so that is likely out of the question.
Sorry if this has been covered, but I am just taking my time with this server and slowly working out all of the bugs, this one I don't have any good ideas that work. I tried adding the panel.example.com to my example.com SSL procedure and that did not change things, example.com still has a mismatch with the Sentora panel subdomain.
Hopefully someone can point me in the right direction here. Thanks.
I want to use example.com on 443 using SSL, but due to the subdomain procedure for panel.example.com, when running the procedure for the domain example.com, it retains the cert. for panel.example.com and gives me the normal non matching URL error in the browsers.
I think I saw something about this here before, but cannot find it now. I am wondering, I don't think Let'sEncrypt has set up for wildcards, so that is likely out of the question.
Sorry if this has been covered, but I am just taking my time with this server and slowly working out all of the bugs, this one I don't have any good ideas that work. I tried adding the panel.example.com to my example.com SSL procedure and that did not change things, example.com still has a mismatch with the Sentora panel subdomain.
Hopefully someone can point me in the right direction here. Thanks.
Everyone makes mistakes, but to truly screw up it takes the root password!
