• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

New big bug with php-fpm and htaccess/protected directory??

sebgonzes

Silver Pleskian
Hi all

I still have no solution for the problem of massive domain with php-fpm on an server (https://talk.plesk.com/threads/prob...eout-specified-has-expired-ah01075-er.335211/) but now have discover what seem an new critical bug with php-fpm, if you put an protect directory or include an .htaccess with "deny from all" in your httpdocs domain, to an domain configurated with php-fpm, you will not be able to access to raiz domain (that is correct), but able to access to subdirectory!!! (that is not correct).

I discover the bug, with an hack and spam to an wordpress domain (that is something comun), we lock access from plesk with an protected directory, but spam still... we discover so that http://www.domain.com is correctly locked, but http://www.domain.com/wp-content/uploads/2015/07/list24.php still accesible!!!! so spam continue and continue. We change config from php-fpm to php-cgi, and all work fine.

What is the problem/bug?? Do plesk can also apport an solution for first problem?

Thanks
Merry chistmas for all!
 
Back
Top