• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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