• 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.

Recent content by KirkM

  1. KirkM

    Issue Migrated Sitejet website error

    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...
  2. KirkM

    Resolved SMTP fails on all new email addresses since Plesk update

    They have disabled the ability to mark as resolved, but it is resolved!
  3. KirkM

    Resolved SMTP fails on all new email addresses since Plesk update

    It was set to hashing. Changing it to Symmetric encryption did the trick. Thank you so much!
  4. KirkM

    Resolved SMTP fails on all new email addresses since Plesk update

    Full error: And yes, the username and passwords are correct.
  5. KirkM

    Resolved SMTP fails on all new email addresses since Plesk update

    A bit more detail - Both the successful tests with the old domains and the failures with the new domains settings are: Username: [email protected] Password: {password} TLS, Port 587 Postfix / Dovecot I have tried: opening all ports on the firewall Disabling the firewall uninstalling the...
  6. KirkM

    Resolved SMTP fails on all new email addresses since Plesk update

    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.
  7. KirkM

    Question Massive price increase for reseller licenses?

    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...
  8. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    Great! ssl=yes works but it looks like you have configured your system to force ssl. Glad you got it sorted out.
  9. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    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.
  10. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    So is encryption working now? My accounts are all working with encryption on all devices.
  11. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    Looks like Plesk has released the mu patch.
  12. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    My mail connections still appear to be encrypted. Are you missing any lines like this: ssl_min_protocol=TLSv1.2
  13. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    I believe that line is now ssl_server_prefer_ciphers=server. They changed the word order in the setting with this new release.
  14. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    I forgot to send a big thank you to King555 for finding the issue with setups without PCI compliance enabled. Mahalo nui loa!
  15. KirkM

    Resolved Plesk Obsidian 18.0.73 Dovecot failed to start after install

    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...
Back
Top