Search results

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

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

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

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%'" >...

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

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

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

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

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

Of course :-) Thanks for the clarifications.

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?

Ah great, so for a fresh Debian 11 installation, AppArmor can stay active. I suggest to mention that on the 'software requirements' page. Can we just enable AppArmor again? Do we have to take something into account?

Thanks for the clear answer, IgorG. Is it planned to support AppArmor for Debian in the future? Is the implementation so different then on Ubuntu, where it is supported? I disabled AppArmor after installing Plesk on Debian 11 on one server. Is there something else I have to do?

Hi On the 'software requirements' page, I read that apparmor must be disabled on Debian. Is that still the case? Thanks Kris

Ahh great. Thank you.

Hello AYamshanov On both servers (Plesk Master and the Slaves): BIND 9.16.1-Ubuntu (Stable Release).

Hello When I delete zones in Plesk (which is the Master DNS), they are not deleted on the Slave DNS servers. Adding and modifying zones is not a problem, but zone files are not removed on the slave DNS servers when they are removed from the Plesk Master DNS server. It seems that no 'rndc...

A temporary solution can be to export a list of all domains on all servers, consolidate the output en import them in the prohibited domain list on all Plesk servers. https://docs.plesk.com/en-US/obsidian/cli-linux/using-command-line-utilities/site-sites.67067/...

Multi Server is only available for Plesk Onyx 17.0 and 17.5.

Sure, if you manage all domains of all clients on all Plesk web servers manually. Or run one (or more) slave DNS servers for each Plesk server. But that means that if you run 20 Plesk servers, you'll need (at least) 20 slave DNS servers. A better solution should be a Plesk upgrade of the Slave...