Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
In my case, it shouldn't be a big problem as I am not dealing with 100s of domains.
Can you point to some articles explaining this method? Is this just done at the DNS level?
I found on GitHub the Plesk-Mail-LetsEcrypt script. The method proposed there is using the Subject Alternative Name (SAN) mechanism (available from Let's Encrypt).
It captures all the domains and adds them using this:
/usr/local/psa/bin/extension --exec letsencrypt cli.php --secure-plesk -w...
What would be the recommended way of adding support of the subdomain mail.domain.tld, so our mail clients do not receive a message saying that there is a hostname mismatch?
At the moment, our Plesk server is sending the certificate for the first installed domain to the mail clients.
Thank you, Peter. I was assuming that it was the case, but I wanted to be sure.
Would it be any evidence on the logs about dovecot not running / placing the files in the proper directories? What should I look for?
I am transferring users from an old server to a new one. In the old one I was using courier-imap and in the new, dovecot. I used the courier-dovecot-migrate.pl script to transform the Maildirs to dovecot.
For a period of time, I have messages delivered by Postfix that never reached the proper...
I have changed my server's hostname (using this guide) because I want to avoid system messages coming from root@localhost.localdomain. The change works, but now every message sent to root is bounced:
May 20 21:49:12 server postfix/smtp[30983]: 859B01008EA5: to=<root@localhost.localdomain>...