• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Issue SSL It! Let's Encrypt Not Issuing Certificate on MX-only Domain

G J Piper

Regular Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Update 1
I have one domain that is hosting email (on an alias mail.domain.com) and webmail.domain.com but is set to "no web hosting" since the main domain's DNS is pointed to another remote server.
Let's Encrypt has been working well on it ever since they allowed mail and webmail domains to be issued even without the main root domain being hosted, until today.
Not sure when it changed, because it is only every couple months the domains get SSL reissued, but SSL It! and Let's Encrypt extensions have been updated since last time this domain was issued, and now it doesn't work. It failed and can't even manually be reissued since the "Get it Free" button is greyed out in the GUI.

Anyone else having this or is it just me because I have an alias running as MX server?
screenshot-20250316-10742 PM.jpg
 
Update:
I was able to trick the GUI into allowing it to issue a new Let's Encrypt certificate for the mail domain services, webmail.domain.com and mail.domain.com alias that is the mail server domain. To do this, I had to enable forwarding in the hosting settings for the main domain, then reissue the certificate and allow it to fail on the forwarded root domain and "www" alias. Even though it failed to save the certificate with those, it still created a valid certificate for the mail server and webmail domain. Then, I turned hosting forwarding back off and all is set.

I strongly suspect that if this doesn't get fixed, however, I will have to do this again in June. I'm glad I don't have a hundred of these mail-only hosting scenarios to deal with!

Let me know if anyone needs me to test anything regarding this.
 
Hello, @G J Piper . I am not entirely sure I was able to fully understand the exact configuration you are having troubles with. Would you mind confirming how exactly is the domain name in question configured, e.g. an alias of an existing subscription with "no hosting" type, the main domain of a subscription, etc. If possible to provide us with step-by-step instructions on how to configure the subscription/domain in question and attempt to reproduce the SSL installation issue would be highly appreciated. Thank you in advance!
 
Back
Top