Username: Peter Debik
TITLE
WP Toolkit causes web server reconfig failure under certain condition
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Obsidian latest MU
CentOS 7.9
WP Toolkit latest version
PROBLEM DESCRIPTION
It is possible to have more than one Wordpress app installation in the same domain. One correct one, but also another one or even more that result from previous installations that have never been removed properly before a new WP site was installed using the WP toolkit.
When a user user uses the "Check security" feature of more than a single one of these WP toolkit entries that are related to the same domain, he can check the "Hotlink protection" checkbox in all these installations, no matter whether they are valid or damaged installations.
When two or more of such checkmarks are set (e.g. one in the valid installation and one in a former installation that was not properly removed), a duplicate entry is written into the web server configuration of the domain for the "fake-hotlink-stub".
This results in an error message when the domain shall be reconfigured or when Web Server Configurations Trouble Shooter tries to reconfigure it:
Unable to generate the web server configuration file on the host <hostname> because of the following errors:
Template_Exception: nginx: [emerg] duplicate location "/fake-hotlink-stub" in /etc/nginx/plesk.conf.d/vhosts/<domainname>.conf:90
nginx: configuration file /etc/nginx/nginx.conf test failed
file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
To resolve this error, a user needs to go into WP Toolkit, open the "Check security" link of the different entries (for the same domain), uncheck the "Hotlink" protection checkbox.
STEPS TO REPRODUCE
See above.
ACTUAL RESULT
Error message when trying to create or modify the web server configuration file.
EXPECTED RESULT
No duplicate entries in the web server configuration files or - even better - make it impossible to create a new WP installation in a domain that already "knows" an existing WP installation in that domain.
ANY ADDITIONAL INFORMATION
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
WP Toolkit causes web server reconfig failure under certain condition
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Obsidian latest MU
CentOS 7.9
WP Toolkit latest version
PROBLEM DESCRIPTION
It is possible to have more than one Wordpress app installation in the same domain. One correct one, but also another one or even more that result from previous installations that have never been removed properly before a new WP site was installed using the WP toolkit.
When a user user uses the "Check security" feature of more than a single one of these WP toolkit entries that are related to the same domain, he can check the "Hotlink protection" checkbox in all these installations, no matter whether they are valid or damaged installations.
When two or more of such checkmarks are set (e.g. one in the valid installation and one in a former installation that was not properly removed), a duplicate entry is written into the web server configuration of the domain for the "fake-hotlink-stub".
This results in an error message when the domain shall be reconfigured or when Web Server Configurations Trouble Shooter tries to reconfigure it:
Unable to generate the web server configuration file on the host <hostname> because of the following errors:
Template_Exception: nginx: [emerg] duplicate location "/fake-hotlink-stub" in /etc/nginx/plesk.conf.d/vhosts/<domainname>.conf:90
nginx: configuration file /etc/nginx/nginx.conf test failed
file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0
To resolve this error, a user needs to go into WP Toolkit, open the "Check security" link of the different entries (for the same domain), uncheck the "Hotlink" protection checkbox.
STEPS TO REPRODUCE
See above.
ACTUAL RESULT
Error message when trying to create or modify the web server configuration file.
EXPECTED RESULT
No duplicate entries in the web server configuration files or - even better - make it impossible to create a new WP installation in a domain that already "knows" an existing WP installation in that domain.
ANY ADDITIONAL INFORMATION
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug