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

Issue .htaccess file does not apply if domain configured to use php-fpm, served by Apache

AndreP

New Pleskian
Ubuntu 14.04.4 LTS‬
12.5.30 Update #40
Apache Webserver,Service Reverse-Proxy-Server (nginx) not running

When setting a domain to use php 5.6.24 to execute as fpm htaccess files are ignored. Setting php to execute as fastcgi everything is working as expected.

I read https://kb.plesk.com/en/128156 saying It was fixed in Plesk 12.5 MU#23. Are there any extra steps to make this work?
 
Try to apply this fix manually:

  1. Download fixed domainVirtualHost file and extract:

    # wget https://kb.plesk.com/Attachments/kcs-63733/domainVirtualHost.zip
    # unzip domainVirtualHost.zip

  2. Backup original file, and replace it with downloaded:

    # mv /opt/psa/admin/conf/templates/default/domain/domainVirtualHost.php{,.backup}
    # cp ./domainVirtualHost.php /opt/psa/admin/conf/templates/default/domain/domainVirtualHost.php

  3. Reconfigure domain:

    # /usr/local/psa/admin/bin/httpdmng --reconfigure-domain <domain_name>
 
Thanks for your reply. I tried the fix, it did not solve my issue.

- I followed your steps and the behaviour did not change
- For a second try i replaced test.domain.com in the php file with <?php echo $VAR->domain->urlName ?> but no success

after going back to the original and then applying the fix again, a diff of /var/www/vhosts/system/domain/conf/httpd.conf and httpd.conf.bak did not show a difference. Is this the file that should be changed?

I forgt to mention the use of Lets encrypt extension for the domain and that the problem affects all domains of the Subscription.

I set up a new subscription for a new customer with 2 domains using Lets encrypt with php 5.6.24 fpm - and i can currently not reproduce the problem.
 
Back
Top