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/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
I used the Plesk migrator to migrate one of a few Sitejet sites to a new server. The first one was a simple site and all went smoothly. It works on the new server and I can edit in Sitejet the same as when it was on the old server.
The second Sitejet website that was migrated seemed to be...
A bit more detail -
Both the successful tests with the old domains and the failures with the new domains settings are:
Username: mailname@domain.com
Password: {password}
TLS, Port 587
Postfix / Dovecot
I have tried:
opening all ports on the firewall
Disabling the firewall
uninstalling the...
When I test smtp on new email addresses on any domain on my server with PHPMailer smtp test script and v7.0.1, I get
Existing domains before the update are fine when do the exact same test but any new ones always fail with the identical setups on the same server and even the same domain.
Read the second paragraph in this section from the 2026 document you listed as Source 2: https://cdn1.plesk.com/wp-content/uploads/pdf/b2a5u/Plesk_Customer_Licensing_Guide_2026.pdf:
If nothing else, they got balls to gaslight like that right to our faces. Either balls or raging contempt for...
I noticed you don't have a reference to the dh pem file at the top. This is getting a bit over my head, but I see that as a difference between our config files.
ssl_server_dh_file=/usr/local/psa/etc/dhparams2048.pem
Not sure if that would be the cause or not.
Here is the breakdown of what happened in the case of King555 and me:
First, they have changed a lot of the settings parameter names and the Plesk update didn't account for them.
One of them is the old parameter name in /etc/dovecot/conf.d/11-plesk-security-ssl.conf
It has been replaced by...