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

Resolved All website on server crashed

SoufianeAb

Basic Pleskian
Hi

When install update for WordPress or sometime clear cache or modify some option all website on my server crashed and see this page on browser

I expect it works in the rest of the countries but for me It crashes for a short time, approximately 10 minutes

by using VPN i can browse all website
 
Last edited:
10 minutes = 600 seconds = default setting in your Fail2Ban IP Address Ban. Plus when you are using a different IP address it works. This is clearly a block imposed by Fail2Ban. Please check your jails and your fail2ban log what is causing this.
 
Is that address your IP address (the one of your Internet connection from where you are working)?
 
Please look into the error_log files of the affected website(s) and look out for the 403 error messages by ModSecurity. These mention and "id" like "id 212870". Add these ids to the exceptions list of the "Web Application Firewall" icon on "Websites and Domains". There will probably more than one id, because normally the Comodo Basic Rule Set reacts on different transactions with some false positives. Add all these ids to the exceptions. But only add the ones that have blocked your own IP. Normally there are two or three rules that are falsely triggered.

Afterwards, the webserver needs to reload the configuration so that the exceptions apply. Meanwhile you can remove the blocked IP from the jails list in Tools & Settings > Security > Fail2Ban.
 
Back
Top