• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Forwarded to devs WordPress Toolkit brakes alle other Sites

B4c4rd1

Regular Pleskian
User name: B4c4rd1

TITLE

WordPress Toolkit brakes alle other Sites

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Version 18.0.27 Update #1
CloudLinux 7.8 (Alexei Leonov)
WordPress Toolkit 4.8.1-3636

PROBLEM DESCRIPTION

If the option: Enable bot protection on a activated WordPress Toolkit Site, this option causes all other sites to stop working.

The WordPress Apache rules are copied to each subscription host file. Is that so correctl? That may only be integrated into httpd.conf and nginx.conf, where WordPress has also been activated or installed.

This rule are copied to all subscription httpd and nginx config and breaks the functionality:

Apache config:
        <IfModule mod_rewrite.c>
            <DirectoryMatch /var/www/vhosts/******/public>
                RewriteEngine on
                RewriteCond %{HTTP_USER_AGENT} "(?:acunetix|BLEXBot|domaincrawler\\.com|LinkpadBot|MJ12bot/v|majestic12\\.co\\.uk|AhrefsBot|TwengaBot|SemrushBot|nikto|winhttp|Xenu\\s+Link\\s+Sleuth|Baiduspider|HTTrack|clshttp|harvest|extract|grab|miner|python-requests)" [NC]
                RewriteRule .* - [F,L]
            </DirectoryMatch>
        </IfModule>

STEPS TO REPRODUCE

- Create a main domain
- Create second domain
- Create a sub domain on main domain
- Create a sub domain on second domain
- Create a wordpress instanz with aps installation on www.maindomain.de/testwp
- Activate ALL security options
- Reload httpd

ACTUAL RESULT

All other host on this subscription are broken. URLs trigger a 404 error. For example: www.seconddomain.de/subdir/ or test.seconddomain.de/subdir/ (Subdirs rewriten by .htaccess)

EXPECTED RESULT

The WordPress configuration may only be added to httpd.conf and nginx.conf, where wordpress is located or installed and not to the other vhost configurations.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM


Confirm bug
 
Last edited:
Hi @B4c4rd1,

This issue was fixed in WPT 4.8.2, which was published a couple of minutes ago. Let us know if you continue to experience any related issues.
 
Back
Top