Hi All,
I have a strange issue that I can not think of a solution for and I am hoping someone on the forum could help.
My servers hostname is server.mydomain.com.
If I issue a LetsEncrypt certificate for server.mydomain.com using this it works fine:
After running this DirectAdmin and all the services are secured and everything works fine.
When I add the domain name mydomain.com to the same DirectAdmin server and then install my Cloudflare issued wildcard origin certificate (mydomain.com, *.mydomain.com) everything works fine for a brief moment.
After around 5 minutes the server certificate seems to change to the Cloudflare Origin Certificate resulting in untrusted SSL for all DA service and the DA control panel.
Is there a way to force the server to ignore the Wildcard Cloudflare Origin certificate that resides within the same domain?
Ideally the server should continue to use the LetsEncrypt issued certificate rather than the Cloudflare Origin certificate.
Thanks.
I have a strange issue that I can not think of a solution for and I am hoping someone on the forum could help.
My servers hostname is server.mydomain.com.
If I issue a LetsEncrypt certificate for server.mydomain.com using this it works fine:
Code:
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single server.mydomain.com 4096After running this DirectAdmin and all the services are secured and everything works fine.
When I add the domain name mydomain.com to the same DirectAdmin server and then install my Cloudflare issued wildcard origin certificate (mydomain.com, *.mydomain.com) everything works fine for a brief moment.
After around 5 minutes the server certificate seems to change to the Cloudflare Origin Certificate resulting in untrusted SSL for all DA service and the DA control panel.
Is there a way to force the server to ignore the Wildcard Cloudflare Origin certificate that resides within the same domain?
Ideally the server should continue to use the LetsEncrypt issued certificate rather than the Cloudflare Origin certificate.
Thanks.