• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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