• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Domain cannot recognize Plesk server SSL certificate

EricRB

Basic Pleskian
I don't know when this problem first started. I just noticed that on a recently added subscription, the customer had selected his own domain LetsEncrypt cert for Mail. But I have set the Server to use the Plesk Server SSL cert for mail, server wide. I know before I could see both the server cert and the domain cert in the drop down box in the domain mail settings, so you could choose either one, but now none of the domains will recognize the Server Cert for mail, even though it is set as the server-wide mail cert. The only thing I did pertaining to mail that could remotely have affected this (longshot maybe) is I had uninstalled SSL-It extension in favour of just having LetsEncrypt there, then when I found this problem, today,(don't know how long the problem is there for), I thought maybe uninstalling SSL-It maybe screwed things up, so I re-installed the SSL-It extension. But that did nothing to fix the problem, and I fail to see why it would or why it would have anything to do with it. I was simply trying anything I could think of. Has anyone seen this problem. CentOS 8 Obsidian 18.0.34 Update #2
 
Back
Top