Problem with Rename WP Login feature

There are 2 points here to clarify:

How do you mean exactly by “encoded my access codes”? I’m sure what this means…

Also, if your IP is whitelisted, then you would have the normal wp-login.php page for login – the rename wouldn’t run for whitelisted IP addresses. So this tells me that the server isn’t seeing the IP address that you think it is.

Thanks,
Paul.

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

Picking up on the last comment.

I have also 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.

Is it possible that the WSF is not correctly handling the list of whitelisted IP addresses ?

I think the problem here is what your server is detecting as your IP address. If it detects your IP address you will by-pass everything. Or if not, you’ll face the same firewall checking as any other visitor.

You could log into your WordPress and review the Audit trail – it marks down the activity with an IP address so you’ll be able to see what the firewall is seeing your IP address as.

That’s the first step. If you find that the IP address you put in the whitelist is the same as the IP in the audit trail for your connection, then there is a bug in there somehow.

Let me know what you find.
Paul.

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.

Unfortunately I have no other reports of the IP white list not working yet. So I only have your report to try and find this problem so far.

I have released 4.3.5 which does, amongst other things, the following:

– detection of whitelisting is streamlined to a single point now and all features run off it. They all use the identical code so if one detects you as whitelisted, they all will.

– in the white list input text area, it prints your currently detected IP address so you can easily see yours when you’re adding to it.

– when visiting any Simple Firewall admin pages and you are detected as whitelisted, there’ll be a permanent WordPress notice telling you that you’re whitelisted and features don’t apply to you. If you don’t see this, the plugin is not detecting you as on the whitelist, or, you have disabled the in-plugin notifications (see Dashboard).

This is all I can do for now to try and find this bug for your hosting environment. If you see anything at all that’s strange pertaining to this, please let me know. The more information and clues to track this down for you, the better, and easier for me to find/fix.

Keep me posted.

SOLVED – I think
=================

Whitelisting of IP addresses does not work if you have an identifier in brackets after the IP address.
e.g. 83.109.158.21 (this is Joe).
It also does not work if you have two ip addresses in the list.

So, Paul, could you please look at the code which processes/parses the ip addresses and bracketed identifiers.

Regards from Joe (and thanks for the hard work)

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

Ah okay, it was the identifiers… I’ll see what can be done about them.

Also, I can’t replicate the multiple IP addresses issue.

Can you tell me what happens when you have 2 addresses? Does it remove them all from the list, or what exactly do you see? When you say it’s corrupt, what’s corrupt?

Are you taking a new line for each IP ?

All the info you can give me the better since I can’t replicate this on my end so I have to dig into it with your clues ??

Cheers!
Paul.

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

Paul – I wonder why you are finding it difficult to replicate the problem which does seem like a PHP interpreter compatibility issue.

I use Apache=2.2.25 Mysql=5.5.23 PHP=5.4.17 hosted at hostgator

Francois – what do you use?

Joe

With version 4.3.6 I’ve added much more thorough validation of IP addresses on the list. So if there’s anything not supported, it’ll be completely removed.

I also just can’t replicate the case where if an IP is on the second line, it’s ignored. I’ve tried it everywhere – top, middle, bottom and it gets whitelisted. :-/

Paul – thank you – everything works for me except the identifier facility.

I tested with 3 ip addresses – whitelisting them works whether input on one line or three.

Identifiers in brackets are just ignored; I can manage without this facility.

Joe

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

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…