Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
litespeed_wiki:config:waf:trusted-ip-in-htaccess [2018/12/18 16:58] Lisa Clarke created from misspelled URL |
litespeed_wiki:config:waf:trusted-ip-in-htaccess [2019/02/14 18:51] (current) Jackson Zhang |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Use "Trusted <IP>" in .htaccess to bypass reCAPTCHA and WordPress brute-force check ====== | + | ====== Trusted IP in .htaccess ====== |
| - | In LSWS Admin Console, Server -> Security -> Access Control -> Allowed List, you can set Trusted IP there with trailing "T". | + | You can set Trusted IPs if you want to bypass reCAPTCHA and the WordPress brute-force check. |
| - | Since LSWS 5.4RC1, LSWS added virtual host trusted IP support, where you use **Trusted 1.2.3.4, 5.6.7.8** in Virtual Host document root .htaccess to unblock blocked IP and make that IP trusted for that vhost. | + | You can do so in **LSWS Admin Console > Server > Security > Access Control > Allowed List** by adding a trailing ''T'' to the IP. |
| - | Virtual Host level trusted IP will bypass LiteSpeed reCAPTCHA and WordPress brute-force security check feature. | + | Since LSWS 5.4RC1, you may also set a Trusted IP at the virtual host level. Use ''Trusted 1.2.3.4, 5.6.7.8'' (where ''1.2.3.4'' and ''5.6.7.8'' are individual IP addresses) in the virtual host's document root ''.htaccess'' file. This will unblock a blocked IP, and make it trusted for that vhost. Both IPv4 and IPv6 IPs can be used as Trusted IP. When IPv6 IP used, please ensure to use ''[...]'' to enclose it. |
| - | All local IP and 127.0.0.1, [::1] will be trusted by default since LSWS 5.4RC1. | + | Virtual-host-level trusted IPs will bypass LiteSpeed's reCAPTCHA and WordPress brute-force security check features. |
| + | |||
| + | Additionally, since LSWS 5.4RC1, all local IPs and 127.0.0.1, [::1] will be trusted by default. | ||