• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.

TLS handshake error. No match between hostname (“example.com”) and certificate.

Azurel

Silver Pleskian
Username:

TITLE

TLS handshake error. No match between hostname (“example.com”) and certificate.

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.10 (Cerulean Leopard)
Plesk Obsidian 18.0.65 Update #2

PROBLEM DESCRIPTION

After delete a domain and add the same domain name as domain alias the mail not working anymore for main domain.

mail client said:
FETCH - TLS handshake error. No match between hostname (“example.com”) and certificate.


Go to SSL in main domain checkbox is empty for "Assign the certificate to the mail domain".

STEPS TO REPRODUCE

Add domain alias without "mail service" enabled.

This remove mail service for main domain.

ACTUAL RESULT

FETCH - TLS handshake error. No match between hostname (“example.com”) and certificate.

EXPECTED RESULT

No error after add domain alias without mail service enabled.

ANY ADDITIONAL INFORMATION

After set checkbox for "Assign the certificate to the mail domain" in main domain, all working fine again.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for your report. Just to make sure we are on the same page:

1. Have a domain example.com configured on the server with a valid SSL certificate installed on it.
2. Remove domain example.com from the server.
3. Add the domain example.com as an alias to exampleMAIN.com while disabling the "Mail service" option for the alias.
4. Your email client fails to connect to mail.exampleMAIN.com with the reported error.

Is that right, or you are trying to describe a different scenario? If yes, please try to elaborate on the steps we need to take and provide us with more details.
 
Thanks for the confirmation. We were unable to reproduce the described behavior. Adding the domain name as an alias has no impact on the mail service or the SSL certificate for the main domain name. Thus, that does not qualify as a Plesk bug. Likely something else was changed on the server configuration that resulted in the error.
 
I had done this with two domains and the problem was present with both. Subscription have two main domains. I use the mails for the main domains myself on a daily basis and it stopped working (mail client log) from the moment I deleted the additional domains and added them back as aliases.

This subscription, for example, also have other bugs.
This subscription was migrated 4 years ago from another server.

In another new subsdcription (created on this server) I can't neither reproduce the issue with mail SSL nor the issue with webstat files.
 
As far as I am aware, the error you are reporting could be caused due to a different value specified in the email client configuration than the server name in the "SSL/TLS certificate" at Tools & Settings > SSL/TLS Certificates > Certificate for securing mail. There might be some issue with the configuration of these specific subscriptions, but it does not sound like a Plesk bug.
 
but it does not sound like a Plesk bug.
I don't understand. The error came due to changes in Plesk and disappeared due to changes in Plesk. Where else should the error be if not in Plesk?
The problem was that the selection was deactivated after delete domain or/and add alias domain (both was made same minute).
1734608649962.png
After enable the checkbox again and reissue certificate, all working fine like a few minutes before I made the changes in Plesk.
 
Thank you for the update. I am not quite sure what triggered that behavior on your server, but removing a domain name and re-adding it as an alias had no impact on the main domain name during test performed on our end. I would suggest opening a ticket with Plesk support for an investigation of the issue on your server.
 
Back
Top