• 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

SSL certificate about to expire warning

105547111

Silver Pleskian
I am getting these emails:

################# SSL Certificate Warning ################

Certificate for hostname 'plesk', in file:
/etc/httpd/conf/httpd.pem

The certificate needs to be renewed; this can be done
using the 'genkey' program.

Browsers will not be able to correctly connect to this
web site using SSL until the certificate is renewed.

##########################################################
Generated by certwatch(1)
 
Hello,

This message is generated by 'certwatch' program that is run daily by crond from the /etc/cron.daily/certwatch file to warn about the imminent expiry of SSL certificates configured for use in the Apache HTTP server. If you receive this message, it means that the certificate listed in the message will expire. If you access the site with expired certificate, the browser shows the warning that the certificate expired and is not valid anymore.

The certificate should be renewed.
Please, take a look at the following article for more information:

http://kb.odin.com/en/827
 
I also just tried to recreate a new self signed with the same info, it does not like plesk for the domain name...

Error: Unable to generate certificate: Some fields are empty or contain an improper value. The values should be limited to 64 characters. If you are using an internationalized domain name, make sure each part of the domain name between dots does not exceed 63 symbols when transformed to ASCII format.
 
Plesk isnt really a valid CN as it should be a FQDN, or for example plesk.com
Try using the name of the server, like plesk.domain.com or w/e you use and see if it likes that better.
 
I have the same problem, I'm getting these daily e-mails even though I already generated a new self signed certificate and set it up in Plesk as the default one and as the default one for the control panel.
 
StefWeidm, The exact same thing is happening to me. I create a new self-signed certificate and do the "secure control panel" procedure to no avail.
 
Back
Top