Fran?ois G.

Same problem here: I updated to 6.3.19, and then it was gone…

WP is completely up to date: 4.6.1.
And the used theme is Twenty Fourteen, without any “crazy” tweaking.

• This reply was modified 8 years, 2 months ago by Fran?ois G..

Same problem here: I am managing over 150 WPs for my customers and myself.
Having to manually correct each of them will take me for ages…

Sorry for the late answer, very busy last days…

It seems to be working fine now.
Thanks a lot!

OK thanks!

I’ll be waiting patiently.
??

Since updating to 4.10.4, I also have strange behaviors regarding IP white listing.
So far I have tested it on 5 websites.

Adding an IP using the “Manage White List” button does not work on 4 of them (#5 is OK).
When I click on “Add IP”, nothing happens.
Yet “Refresh” is operational everywhere…

Even stranger: adding it, using the deprecated form in the Dashboard, works on 3 of them (the one that is completely OK, and 2 where “Ad IP” is not functional).

In all cases, I can delete the already defined IPs without problem.

Quite confusing…

It makes sense…

Regards,
Fran?ois

Thinking further, I think this behaviour is quite puzzling, because it means that the “Ignore Administrators” option is simply ignored in that specific case…

You are right indeed!
That option was differently configurated on those two WPs.

Thanks for the explanation.

I would recommend a note, to be dispalyed next to the redirect option (or next to the “Block Leading Schemas” option), to avoid the same confusion from other users…

Regards,
Fran?ois

And when the not whilisted address trie to connect, here is what appears in the Audit Trail Viewer:

Event
firewall_block

Message
Page parameter failed firewall check. The offending parameter was “redirect_to” with a value of “https://XXX.XXX/wp-admin/”. Firewall Trigger: Leading Schema. Firewall Block Response: Visitor connection was killed with wp_die() and a message.

Username
unknown

Category
3

It seems that the redirect option is a bit unstable, or am I wrong?

Correction:

The renaming options is no longer correctly working on my main WP test website, as described above.
But it is OK on another WP, where I have only activated it once, and not played with multiple whitelisted addresses.

Repeatedly adding and deleting them must have corrupted the plugin somewhere…

The situation today, with version 4.3.6.

Good:
– Multiple whitelisted IP addresses are identified.
Identifier is erased when validating them, but the system works.
– Renaming the login page does not affect whitelisted IP addresses.

Bad:
– The “Rename The WordPress Login Page” option is totally useless if you do not have a static IP address.
Because, when activated, any address that is not whitelisted is NEVER be able to connect, the end message is always:
“You were blocked by the WordPress Simple Firewall. Something in the URL, Form or Cookie data wasn’t appropriate.”

Tested on several computers, to avoid browser cache problems.

Regards,
Fran?ois

OK…

It is even trickier than I imagined!

When you add a second address (on a second line), only the second address is whitelisted.

The first one becomes ignored, and is greeted with the “I’m a human” message.

Regards,
Fran?ois

You are totally right!

I have just deleted the identifier in bracket, and when validating, I had the (never seen before) message:

Notice – You should know that your IP address is whitelisted and features you activate do not apply to you.
You IP address is: xxx.xxx.xxx.xxx

Then I de- and re-connected and tadaaaa, it works!

Also correct, a second address, on a second line, corrupts it all again.

And if the “IP Whitelist” option works, then the “Rename WP Login Page” option works as well.

Regards,
Fran?ois

The audit trail does show the correct IP address.

Moreover the “I’m a human” problem has appeared on all my WP (after updating the WSF), that are scattered on several different servers, at several different locations, using all different OS.

And I notice that I am not the only one to report that problem.

Therefore I think I can safely say that there is a bug…

Finally, to be complete, it is still present, after updating to version 4.3.4.

1°) I enter the new url in my navigator, and it leads me to the login page, so far, so good.
There I enter my username and password and click on the Connect button.(*)
That is when I get the above mentionned error message.

2°) I am connecting from a whitelisted IP, and yet the only working URL is the new one, that remains as it, when the login page appears on the screen.

Your idea about the server not correctly seing my own IP address, could be right, because I have noted that with this last version of the WSF, the “I’m a human” notification now keeps being displayed, even though I am connecting from a whitelisted IP address.

Regards,
Francois