wp-admin and single product page redirects to 127.0.0.1

Hi again, looking at the other aiowps tables, there is 14551 rows in the aiowps_events – is this normal and necessary? Perhaps has nothing to do with the issue above – but what is this doing – should I remove some of these perhaps (just for cleanup).
Many thanks. Peter

Hi again,
Went to google for more advice. Then your own FAQ was the first result (searching for WordPress login 127.0.0.1), the advice was to go into the admin panel and check the Permanent block list. Funny enough, here I found my IP adress (from whatsmyip in Safari), clicked unblock, and then tested. Now it works again going in via Safari. So some times the more easier steps is the one to try first (I think we went too fast into the database tables, that now was all cleared out in these two tables). I hope WP Security will find the new attempts and put them in the tables again if they try.
So, issue is now solved. Thanks for your help.

Just one more questions, now that I am in the tables in the database, I see we have 14144 aiowps_events – does this not seem a lot? What are these for, should I remove them perhaps?

Many thanks, Peter

Hi @sevenpeter

Event logs entries 15k approx should be cross check what those events are? I do not consider it normal, but also it is not that much high.

if it is regarding failed login attempt etc, Its stack trace to be analysed. can you please share it with https://pastebin.com/ before clean up.

So we can minimize such events due to bots.

Regards

Hi,
I made an export from the database to pdf. See attached file. Hope that makes sense. Am sending it in wetransfer link instead, see this: https://we.tl/t-sUzkaIgMjn

Is this normal? Feels like A LOT of information here, to what use? Is there a way to set the clearing of this (if it is not needed) more often? How much statistic in this table should be normal (if good to have)?

Many thanks in advance for your help.

Best regards, Peter

Hi @svenpeter

If I cross check the PDF mostly seems 404 error. Make sure you have WP Security >Firewall > 404 detection on.

You can delete those events have 404 as event_type IF possible keep those IPs list, so in future you can black list with most having 404 errors.

You can define below constant in wp-config.php so instead 90 days it have only last 30 days events log which will reduce its size.

define('AIOS_PURGE_EVENTS_RECORDS_AFTER_DAYS', 30);

Regards

Hi,
Yes, all you propose above is now made. We had the 404 detection set on “on”. Have now deleted all 404 in the _events table. Added the most common IPs to the block list. And set the 30 day limit for logging. So now should be better in the future. I will keep looking a while in the table to see what comes in the close future.
Many thanks for helping out.
best regards, Peter