Restrict By IP Not Appearing to Be Working Properly

Hi,

Please send me the debug data from my plugin, to mimic the same settings on my environment.

Have a nice evening,
Iulia

Thanks for your reply @iulia-cazan! I’ve just sent an email with this post title as the subject line through your website contact form with more info and a link to the debug data.

Hi @iulia-cazan, it looks like the files haven’t been downloaded yet. I would rather not post the transfer link here, but it expires on 19 Jan. Please confirm if you received the links via the email I sent through the contact form on your website.

Thanks!

Sorry about this, will check my emails again and see if I missed it.

• This reply was modified 1 year, 10 months ago by Iulia Cazan.

I confirm I found the email and downloaded the debug data. Will troubleshoot and let you know when I have more details.

Hi,

I run all the tests and also installed the “WPS Hide Login” (I saw in the data you sent you are using it). All seems to be working as intended, could not replicate an issue.

However, I saw you are allowing 127.0.0.1, which looks like a local setup. Please remove any other local-like IPs (127.0.0.1, ::1) from the allowed IPs if you are testing in a live environment.

Additionally, you could disable temporarily the “WPS Hide Login” plugin, to exclude an incompatibility between the two plugins.

Let me know how it goes.

Regards,
Iulia

Hi,

We’re still experiencing the issues. In original troubleshooting and again now when troubleshooting with the new info, we’ve disabled the WPS hide login plugin to eliminate that from being an issue. Whether the WPS Hide Login is active or not, when the filter is on, we cannot access the login from any IP, regardless of settings.

The IP we are attempting to allow, is a VPN public facing IP. Would that potentially be causing any issues? I don’t see why it would since that is the IP registering when on the VPN, so that should be what the login filter sees.

A few notes from this troubleshooting session: When the filter is active, we are not able to access the login page at all, even from the specified IP address. We’ve tested by using a different, clean browser with no cache/history, on different networks, and on different machines, all to the same conclusion. When the filter is on, even if we allow our personal IPs, we are forbidden from the login.

Regarding the local IPs, those local IPs are added when we save the filter. When we load into the IP Filter section, it displays the current IP address. We then add only the specific IP we want to include, and hit save. When the page displays the new filter, it includes the local and the ::1 address.

I’ve uploaded a recording of the entire process, from activating the plugin, putting in the IP address, showing the local IPs being automatically added, and then trying to access via the allowed IP which shows as blocked. I’ll send this recording via your website form.

Thanks!