You can also enable reCAPTCHA on an individual virtual host that is under attack, while leaving other websites disabled. Once the visitor has been inactive for more than 20 minutes, reCAPTCHA is once again enabled for that visitor's next request. This validation protects the server against HTTP Flood and other DDoS attacks.Īfter passing the reCAPTCHA validation, the visitor is temporarily whitelisted as long as they continue to browse the site. When a visitor accesses the website, they will need to go though reCAPTCHA validation. This sensitivity setting will be inherited by all control panel Apache virtual hosts and LSWS native virtual hosts unless overridden at the virtual host level. You may adjust these values according to your needs. It may be overridden at the virtual host level.įor other options, hover over the ? symbol to view detailed information about that option.įor demonstration purposes, we will set Trigger Sensitivity to maximum ( 100), and reCAPTCHA Type to Checkbox.

It will enable the reCAPTCHA feature for all control panel Apache virtual hosts as well as LSWS native virtual hosts globally. This is the master switch and it is required for both a control panel environment and an LSWS native environment. Enable Globally at the Server Level ¶Īccess the WebAdmin console via Navigate to Configuration > Server > Security > reCAPTCHA Protection Please see the WP-Protect Guide for more information about that. ReCAPTCHA may also be used as a method of WordPress Brute Force Attack Protection. LiteSpeed cPanel Administrator's Handbook - LiteSpeed Documentation reCAPTCHA Returning 403 and Dropping Connection.Advanced Configuration: Define reCAPTCHA Actions through Rewrite Rules.Override for LiteSpeed Native Virtual Hosts.Override/Disable for Apache Virtual Hosts.Override/Disable at the Virtual Host Level

Protect against google recaptcha bypass