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

    Resolved Update Plesk via CLI

    Hi I want to control and update Plesk via the CLI. Some questions: What is the difference between plesk installer update and plesk installer upgrade ? How can I run an upgrade from eg 18.0.57 Update 1 to 18.0.57 Update 2? How can I upgrade the extensions via CLI? Thanks
  2. K

    Issue 'Apply DNS Template Changes' after each DNS record update

    I understand what that is meaning, but there is nothing else to apply than the client's own record change. These are the steps: Client changes / adds a new DNS record in his zone. Client clicks 'apply' on the question 'The changes you made to DNS records are not saved yet. The changes are...
  3. K

    Issue 'Apply DNS Template Changes' after each DNS record update

    Hi When a client changes a DNS record, he mostly (mostly, not every time) he get the following message after saving his change and 'apply the zone update'. The global DNS template wasn't changed.
  4. K

    Resolved Can not change DNS server-wide settings

    Thanks @Yaroslav_T, that fix does work.
  5. K

    Resolved Can not change DNS server-wide settings

    Hi In DNS Settings > Server-wide settings, I want to add the notify yes; also-notify { ... } records. But when I save these changes, I get this error: The log from panel.log: It's a fresh Plesk installation on Debian 12. Thanks
  6. K

    Issue Limitations in Reseller plans overruled in Reseller's Service Plans

    I get the 'cosmetic' side of the issue. But for resellers (even technical-minded ones), it is very confusing why their clients can not use some stuff that they have allowed them to do. So indeed it is a not a technical bug, but a bug that is very confusing because resellers don't know what is...
  7. K

    Issue Limitations in Reseller plans overruled in Reseller's Service Plans

    Thanks, Peter. That's quite ambiguous for the reseller. They assume that they can use these options and use it in their own Service Plans; they don't know they can't. Shouldn't it be more logic that resellers don't see the options that are not active in their Reseller Service Plan?
  8. K

    Issue Limitations in Reseller plans overruled in Reseller's Service Plans

    Hi Situation I've created a reseller plan with some limitations, like: unchecked 'backup [...] remote storage unchecked 'WP Toolkit Smart PHP Update' unchecked 'Database server selection set '0' value for 'WordPress websites with Smart Update' Problem A reseller with this plan can still...
  9. K

    Question Is Debian 12 fully supported?

    Thanks for the info.
  10. K

    Question Is Debian 12 fully supported?

    Thanks for the confirmation, @yborzykina Any idea if and when these components will get support?
  11. K

    Question Is Debian 12 fully supported?

    Hi Does Plesk support Debian 12 and all components? For Debian 11, some components like WatchDog, Mailman, Webalizer and ModSecruity are still not available (regarding to this article). Do all components work, or are there any known incompatibilities? Thanks
  12. K

    Question Remove PHP 7.4 and upgrade sites to PHP 8.1

    Or even simpler, just select the PHP version we will remove: plesk db -Ne "SELECT d.name, h.php_handler_id FROM domains d, hosting h WHERE d.id=h.dom_id AND d.htype = 'vrt_hst' AND h.php='true' AND h.php_handler_id LIKE '%php74%'" > /root/domains_hosting_php_enabled.txt
  13. K

    Question Remove PHP 7.4 and upgrade sites to PHP 8.1

    Okay, I found the column 'php_handler_id' in the 'hosting' table. So I'll use something like: plesk db -Ne "SELECT d.name FROM domains d, hosting h WHERE d.id=h.dom_id AND d.htype = 'vrt_hst' AND h.php='true' AND h.php_handler_id NOT LIKE '%php82%' AND h.php_handler_id NOT LIKE '%php81%'" >...
  14. K

    Question Remove PHP 7.4 and upgrade sites to PHP 8.1

    I see the query: plesk db -Ne "SELECT d.name FROM domains d, hosting h WHERE d.id=h.dom_id AND d.htype = 'vrt_hst' AND h.php='true'" But that selects all domains, also the domains using PHP 8.0 and 8.2 would be moved to the given selector. How can I search for only domains excluding specific...
  15. K

    Question Remove PHP 7.4 and upgrade sites to PHP 8.1

    Hi We are planning to remove PHP 7.4 from our servers. Before we do this, we want to move all sites with PHP 7.4 enabled to PHP 8.1. How can we change the PHP handler via CLI from all sites using PHP 7.4 to PHP 8.1? And leaving sites that are using PHP 8.0 or 8.2 untouched? Thanks
  16. K

    Issue HSTS issue with www forward

    There is no output. Without strict: 301 Moved Permanently. And a location header to forward to the domain including www.
  17. K

    Issue HSTS issue with www forward

    Hi I have a question / problem with the SSL-IT HSTS implementation. When I test the hosted websites on ssllabs.com, then the result is that HSTS is not configured and OCSP stapling is not active. When I test on hstpreload.org, I get two errors: Error: No HSTS header Response error: No HSTS...
  18. K

    Question ModSecurity Atomic rule set on Debian 11

    Hi In the Plesk Help Center, in the article 'Does Plesk support Debian 11' it is stated that ModSecurity Atomic rule set is not supported. Is there any prospect in supporting the (Advanced) Atomic rule set on Debian 11? What rule set do you use / advice? Thanks Kris
  19. K

    Resolved Apparmor on Debian

    Of course :-) Thanks for the clarifications.
  20. K

    Resolved Apparmor on Debian

    Is that the case for each dist-upgrade for a specific reason, or was that just a problem when upgrading from Debian 10 to 11?
Back
Top