• 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. F

    Resolved Mailing list not working

    FYI: request (95247221)
  2. F

    Resolved Mailing list not working

    OK, I'll open an official support ticket then. Thank you for your help here.
  3. F

    Resolved Mailing list not working

    I tried that, and then on my server the list name becomes [email protected]. I could live with that but then the Plesk-generated "Manage list URL" https://lists.lists.domain.com/mailman3/postorius/lists/<list email address> which I can't secure. My wildcard certificate can only secure...
  4. F

    Resolved Mailing list not working

    Hello, thank you for replying. We are in a situation where we do host Mailman mailing lists for customers whose web site and email are hosted on other servers. I'm currently testing Plesk implementation of Mailman3 on Debian 12. When I go to generate a Lets Encrypt certificate for the domain I...
  5. F

    Resolved Mailing list not working

    Testing new Mailman3 integration on Plesk Obsidian Version 18.0.60, on Debian 12: Dear @IgorG Please improve Plesk and Mailman/Let's encrypt integration. We manage DNS on another server and can not use wildcard LetsEncrypt certificates: make it so lists.<domain> can have have its own LE TLS...
  6. F

    Resolved the SSL certificate for mailman

    That's not good enough... lists.<domain> needs to have its own LE TLS certificate like webmail.<domain> does.
  7. F

    Resolved How to remove Sectigo SSL?

    Although the Sectigo extension is not installed and does not show in the extensions list, it still shows as an option in the SSL IT. extension How can we remove it from SSl IT?
  8. F

    Resolved Smtp Smuggling advisory

    I asked Plesk support this same question about our servers, here is their answer received today: Thank you for waiting, we've got an update from Security Team. Indeed, Plesk servers are affected by this vulnerability. Plesk ships own Postfix 3.5.x packages for RHEL<=8 (and its forks) and Ubuntu...
  9. F

    Resolved Plesk SQL query to find domains and PHP versions

    I found this to get the WP version: select dom.name, dp.val, h.php_handler_id from domains dom LEFT JOIN dom_param dp ON (dom.id=dp.dom_id) where dp.param="wapp" or dp.param="wapp-version" How can I combine the two queries?
  10. F

    Resolved Plesk SQL query to find domains and PHP versions

    Hi, Igor, Thank you for this. How would I also get the Version of WordPress used by those domains?
  11. F

    Resolved How to update cURL on CentOS 7.9.2009 (Core) and Plesk Obsidian 18.0

    Also update the package version in the Plesk panel with: plesk sbin packagemng -sdf
  12. F

    Important Skins and Color Schemes

    Out Brand Theme was custom and has now disappeared after the latest Obsidian upgrade (18.0.25). Our logo is Dark looks ugly now: We do need the light skin. Please bring it back, thanks
  13. F

    Plesk 12.5.30 update failed

    Hello, I'm experiencing the same issues Dimitris was having: After server upgrade on a CentOS6.9 from Plesk 12.0.18 to 12.5 Plesk is slightly disfunctional. - SSL certificates are not showing in subscriptions tools (They are in hosting settings) - Blank page for Backup Manager - Plesk top Menu...
Back
Top