Whitelist does not work with Advanced Google reCAPTCHA

Hello @estalhun ,

Sorry for the inconvenience caused.
Would you please tell us which captcha version you are using? As we have tested on our side it’s working fine.
And would you please log in to WordPress admin and then go to Loginizer Dashboard and check Your IP and compare the IP with the IP you find on https://whatismyipaddress.com/
If the IPs are different then, please set HTTP_X_FORWARDED_FOR as the IP method which you will find on the Lognizer dashboard page beside the Your IP field.

Regards,
Loginizer Team

Dear @loginizer

I use v3 and I have fixed public IPv4 address. I noticed the problem exists only when I use the LiteSpeed caching plugin.

Best regards,
@estalhun

Hello @estalhun

Would you please tell if you are using object Cache? And would you please tell what error do you see when you try to login. I mean the error before you got locked out.

Regards,
Loginizer Team

Hello @loginizer

Yes I use Redis. I see the recaptcha failed and standard notification about xy attempt left before lockout.

I figured out that this issue is permanent if I use Localize Resources on Google recaptcha js.

Hello,

Would you disable Redis cache and disable Localize Resources and then try to Login tell us if you face the same issue.
And do are you using a custom login page?

Regards,
Loginizer Team

Hi,

If I disable Localize Resources then it works well in the most cases. But sometimes I have to use private browser window. Object cache does not matter.

Best rregards,

Estal

Hello @estalhun

Does the your IP matches with the IP that Loginizer is showing on the Loginizer Dashboard?

Dear @loginizer,

Of course my static, public, external IP address appears in the list.

But I have more information. My colleague has same problem on an other site. Both site has the All In One WP security plug-in free too. We use it to lockout specific login names instantly.

https://drive.google.com/drive/folders/14b9h9LjEgFcMeQxjKV-FJQ0B-VIQXEHy?usp=sharing

Best regards,
@estalhun

Hello @estalhun ,

Thanks for the info, I tried the same configuration as yours to reproduce the issue, but was unable to do so, as it working totally fine for me.

Will it be possible for you to contact us at https://softaculous.deskuss.com/open.php?topicId=16 we will need to debug it to find out why you are facing this issue.

Regards,
Loginizer Team

@loginizer

The problem is solved with your help, thank you very much!

The solution is: if you use the white list, add start and end address even though the start and the end address is the same.

Regards,
@estalhun

Hello @estalhun ,

Glad to know that the issue was resolved. Just wanted to add to your solution. You won’t require to add End IP, it will get added on its own in the case of a Single IP, just need to keep in mind to check if both Start IP and End IP are shown in the list.
The reason why the End IP was not there was because when you whitelisted the IP you must have done it in an old version of Loginizer.
But now if you have a single IP then Loginizer itself adds the End IP.

Regards,
Loginizer Team