• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Question CNAME and SSL

Chepplesk

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
18.0.58
Hi, I need to point a domain of one of my client (crm.tenant.ext) via CNAME to a site of mine hosted on Plesk (tenant.myserver.ext).

crm.tenant.ext CNAME tenant.myserver.ext

My client created the CNAME , technically everything works except the Let's Encrypt SSL certificate. I get the error SSL_ERROR_BAD_CERT_DOMAIN because the certificate is valid only for tenant.myserver.ext and not for the source domain (crm.tenant.ext). My server has Plesk Obsidian updated to the latest release, and Debian 11. How to fix it? Thanks to all
 
You could create crm.tenant.ext as a new domain in the same subscription ("Add domain" button), but enter the same document root directory into it that tenant.myserver.ext uses. When crm.tenant.ext resolves to tenant.myserver.ext, it should be possible to issue a domain validated SSL certificate for it.
 
Back
Top