alanpae

Done. ??

Just found it.

Adding a * to filter, show user agents, then empty the other one and then I can finally delete everything.

Thanks much,
alan

Delete gives pretty much the same error message. A quick browse just shows basically who the author was. Since it’s just me does this table even do anything? ??

thanks,
alan

The smartest way is to learn SQL. ??

Or you can use phpMyAdmin if your hosting provider provides it or if you have it on your self hosted site.

I actually use a script that I just run using the SQL command line option of phpMyAdmin:

TRUNCATE wp_itsec_lockouts;
TRUNCATE wp_itsec_log;
TRUNCATE wp_itsec_temp;

Or there are other plugins that will let you enter SQL commands directly to the database as well.

alan

A better way is to just empty the 3 tables with the itsec prefix.

Updated to 3.1.2 and that fixed it.

Thanks for that. It seems most of these are just bots using the generic name of admin and trying to brute force the site.

I installed something – not sure what – that added a check box on the logon page that simple says, I’m a human. If you don’t check it then you can’t logon. No more emails saying someone tried to logon with a non-existent account anymore. ??

alan

Better WordPress Security was the plugin

Thanks,

Figured out which plugin was causing this and got it disabled.

alan

That allowed the web site to work but causes 500 errors on the admin pages. So I just removed all of their code altogether.

Everything works again. ??

Thanks,
alan

Marking as resolved.

Thanks for the edit and the explanation. Should I just delete the other one then altogether?

attached file sent.

Now I know they’re reading this. File Sent. ??

Someone from Go Daddy must be reading this. When I can get access to the File Manager again I’ll send the file.

The secure.htaccess file looks ok to me. Leave an email address and I’ll email it to you and you can tell me what’s wrong with it.