• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Plesk SSL certificate clear

Vitali

New Pleskian
Server operating system version
linux
Plesk version and microupdate number
00
Problem with letsencrypt common name

It seems that the correspondence between the dns and the domain was not yet well established, which caused that when issuing the ssl certificate, there is no mismatch between the domain and the common name, but the common name points to the server and does not correspond to the domain. The solution for this is to issue a new certificate in which there is a mismatch between the domain and the common name. The problem I have is that in plesk the wrong certificate is the one that continues to load and not the new one, already corrected and loaded. That is, in the new certificate there is already a correspondence between the domain and the common name, but plesk continues to use the wrong certificate, which is why my website still does not properly resolve the ssl certificate. I have already unassigned certificates, deleted certificates and nothing works.

I have already been reading possible solutions, some say that you have to wait but I have already waited more than a week and the problem is not corrected. Others say that you have to restart plesk or repair web in ssh but the provider does not give me those options. Is there any other way to correct this problem? I don't have the server linux version and plesk version requested below either.
 
Hello, @Vitali . If re-issuing the SSL certificate or issuing a new certificate for the domain name in question did not solve the issue, what you could try is the Plesk repair utility (it requires admin access to the server):

plesk repair web -y

If your host doesn't provide such access, please ask them to run it for you. Then change the SSL certificate from the dropdown in Plesk > Domains > example.com > Hosting & DNS > Hosting > SSL/TLS support to "Let's Encrypt example.com (example.com)". I hope that helps.
 
Back
Top