问题原文
原帖链接 · RDAxRoadkill · CC BY-SA 4.0
I've got a Plesk setup which issues Letsencrypt certificates and hosts part of my client websites. When passing the _acme-challenge and receiving a wildcard certificate / installing said certificate it seems that part of the subdomains which aren't hosted with me still give a certificate error.
My setup in the DNS is currently as follows:
example.com- A informational website hosted on my Plesk server.dev.example.com- A separate dev site hosted on another IP address eg192.0.2.12live.example.com- Another application entirely, hosted by me and working with the current SSL
As far as I understand this, the other party from dev.example.com also needs to install a wildcard certificate on their end? Or is there something wrong with my certificate itself.
已采纳解答
原帖链接 · Stephen Ostermiller · CC BY-SA 4.0
A certificate has to be installed on every web server hosting content for the domain. The wildcard certificate you obtain and install on your server will only cover subdomains hosted on your server. If your client has a subdomain hosted by a third party, that third party would need their own certificate.
The dev subdomain doesn't have to have a wildcard certificate. It could have a non-wildcard certificate that only covers dev.example.com which is obtained separately from the wildcard certificate that Plesk gets. In other words, the company hosting the dev subdomain could use the HTTP challenge protocol to get a LetsEncrypt certificate without having any access to your server or DNS.
Another option would be for your client to copy the certificate, private key, and chain from the Plesk server to the server for the dev domain. I would not recommend doing so unless they could automate the process. LetsEncrypt certificates expire every three months. Relying on manual copying for such short lived certificates is not usually reliable enough.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
