• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Problem with SSL from Plesk for E-Mail in Thunderbird

ealexey

New Pleskian
Hello,
I don't know if the Problem are in other Mail-Programms (like Thunderbird), I have this one.
1 week ago I haven't no problem. Suddenly I began recieve in Thunderbird message (pop-up Window) to accept a SSL-Sert. but, thus the cert is obsolete (valid until 14.02) I have even no possibility this to accept: the button are just deactivated.
I saw the details of cert, it is from Plesk.
I loged in into Plesk, went to tools -> SSL/TLS Certificates and created a new one. The old was in use so I went to tools -> ip addresses -> ip address and setted here SSL/TLS certificate to new created. Then I'm back to -> SSL/TLS Certificates and setted here the new created as default the old was not in use and I deleted it. Restarted Plesk Service with: service sw-cp-server restart.
If I open Thunderbird I am always asked about (old) cert and cannot recieve emails from server.
I tried to reconfigure all with /usr/local/psa/admin/sbin/httpdmng --reconfigure-all and again restarted - nothing.
Can you help me, how to fix it.
I use Let's Encrypt and tried to recreate the cert.
The webmail I can open without some problem, I see there is used the correct cert from Let's Encrypt. Website use the correct one too. Just the Thunderbird for no apparent reason try to set expired and not correct cert from Plesk, although for websites are created the certs with Let's Encrypt.
I tried it with differents port / protocos too: 110 with STARTTLS and 995 with SSL/TLS.

Attachments:
Screenshot - 20_02-o.jpg if TB connect to server
Screenshot - 20_02 002-o.jpg - if I click to get I cert
Screenshot - 20_02 003-o.jpg - if I click to view a cert

Thanks
 

Attachments

  • Screenshot - 20_02-o.jpg
    Screenshot - 20_02-o.jpg
    201.1 KB · Views: 12
  • Screenshot - 20_02 002-o.jpg
    Screenshot - 20_02 002-o.jpg
    182.4 KB · Views: 8
  • Screenshot - 20_02 003-o.jpg
    Screenshot - 20_02 003-o.jpg
    145.7 KB · Views: 9
As I understood the problem was that plesk certificate expired and couldnt updated. In SSH I opened ls -la /usr/local/psa/admin/conf/ there moved httpsd.pem to httpsd.pem.sav:
mv /usr/local/psa/admin/conf/httpsd.pem /usr/local/psa/admin/conf/httpsd.pem.sav
I didn't find how to renew or recreate such cert (.pem) for plesk by using a SSH. Tried to create new one with plesk panel in tools -> SSL certificates. But nothing.
But I oened ext. Security Advisor (wich was installed), there in tab "System" click on "Plesk is not secured with a valid SSL/TLS certificate", Let's encrypt created a valid cert. In tools -> SSL Certs this cert was assigned to "Certificate for securing Plesk", but for "Certificate for securing mail" -not. Clicked on "Change" and choosed new created cert from Lets Encrypt (with "server pool" on the End). If nessesary click on "make default".
After that all works, I can accept this certs in TB. The Question is, why TB call the def.cert from server and not certs from domains, which are setted as well. But it is another topic
 
Back
Top