Blobfolio

Hey Steady,

Thanks for the update, and I’m glad it’s working now!

In the next release, I’ll include that IP validation test as part of the settings page itself, so it can be made clear when there are issues that could prevent logging.

Hey Steady,

Would you please let me know what other plugins you have installed? I’m going to try to recreate your setup and see if I can break something too! Thanks!

Hey Steady,

I’m sorry, #3 requires a little bit of PHP. But as an Arch user, I’m sure you’ve had to do worse!

$_SERVER[‘REMOTE_ADDR’] is a PHP variable that should return the IP address of the visitor. The easiest way to see this and other variables is to make a quickie PHP file with the following code:
<?php phpinfo(); ?>

It is this variable that Apocalypse Meow tries to evaluate prior to logging a log-in attempt. If the value returned by this variable is not an IP, or falls within private or reserved ranges, or matches that of the server itself, then it can’t do its job, and so doesn’t log anything.

To see how the above test actually evaluates on your server, please create a quickie PHP file somewhere on the server with the following code:
<?php var_dump(filter_var($_SERVER['REMOTE_ADDR'], FILTER_VALIDATE_IP, FILTER_FLAG_NO_PRIV_RANGE | FILTER_FLAG_NO_RES_RANGE)); ?>

That should either print your IP if your IP is okedoke, or False. If it is False. Please let me know if you get your IP or False.

Thanks for taking the time to help debug this plugin!

Hey steadybright,

Thanks for all the details! Would you please check/confirm three things for me?

1) Did the database tables get created? You should see *meow_log and *meow_log_banned (where * is your WP prefix)?

2) Are you behind any sort of proxy that might be returning a reserved/internal IP instead of the user’s actual one?

3) Is the $_SERVER[‘REMOTE_ADDR’] environmental variable being populated?

Thanks for following up, igemini1. Do you have access to your server’s error logs? It sounds like a fatal error is causing WP to exit without printing the rest of the page, however I am unable to reproduce this behavior on any of my local servers. Any additional details you could provide would be very helpful! Thanks!

Hi igemini1,

I’m sorry for the confusion, but there is no separate “Install Now” link. The Tools menu listing for Look-See will either take you straight to the scanner, or prompt you to install hashes for your version of WordPress (if they aren’t already installed).

Thank you so much! I’ll close out the issue if you report back favorably. ??

Actually, salsaFire, I think I tracked the issue down to Firefox not liking the plugin attempting to reload the page upon scan completion. I pushed through an update 13.08.3. Would you please give this a try and see if it works for you?

Hi salsaFire,

Thanks for contributing! Out of curiosity, did it get stuck at the 2000 mark, as it did for Brain? And are you using Firefox?

I’m going to go ahead and mark this ‘resolved’ since no further details have been shared, and no other users have reported experiencing the issue.

If you are still having trouble, please re-reply! Thanks!

Hi Brain,

Thanks for reporting this!

Do you have access to your server’s error logs? If so, do you see any timeout errors corresponding to the scan attempts? Generally when a scan gets “stuck”, it is because the server stopped executing the script prematurely. Most of the time this can be fixed by limiting the file scan size to something smaller, like 1MB or so (your average PHP file will be much, much smaller than this).

labarbiche,

The change was actually rather simple, so I’ve managed to push out an updated version this morning (13.04)! I tested it with both MyISAM and InnoDB storage engines, so you should be good to go.

Thanks again for your feedback!

Thanks for bringing this to my attention, labarbiche!

I’ve run into this issue on another server using InnoDB as well. I’ll be releasing an update with a new table structure this week that should work with that engine. I’ll post back here once it’s up.

Thanks for bringing that to my attention!

I’ve just pushed through an update (1.3.6) that should fix that for you (and everyone else running PHP 5.3+).

Oh, great! Haha. Thanks again for helping me debug this!