rominatrix

Thank you very much for your reply! I guess I will have to wait until we can update our php version then. I tried manually updating the plugin but it’s giving me the same error that you mentioned is related with our outdated php version. It’s something we’re working on but still haven’t been able to do.

Thanks again!

Hi Gerroald!

Thank you for the follow-up.

Even though we are aware that sometimes emails can take their time, we were always able to receive them. However, we did both tests you suggested and I can confirm that both tests were successful:

> Wordfence Test Email
> Wordfence activity for 22 enero, 2020 on [our domain]

I’m wondering if there’s any other parameter that might be bothering here that I might not have mentioned and that’s preventing Wordfence from sending us all the alerts? Another idea I was thinking of is the combination of an older version of WordPress and the version of Wordfence we have, as I mentioned in my first post.

Do you think that any of that could be at play here? It’s so important that we receive the alerts, specially the high ones and we’re not understanding what’s happening cause even if there are many setup options they are pretty self explanatory.

If there’s any other information I can provide that might shed some light on this issue please let me know.

Thank you again,
Romina

Hi Gerroald!

Thanks for your reply. We’ve tried it as you suggested and set it up to “high”, we ran another scan and even if the scan detected the high issue, we did not receive the email (wordpress is correctly sending emails and the email account is working and it hasn’t gone to spam).

What else do you think we could try?

Thanks again!
Romina

This is embarrasing but I’m glad to say this issue is fixed.

After that “locked out” message I starting looking up on that term and found out it’s related to wordfence blocking you for a specific reason. While on the live traffic my ip showed up only once, i found it odd that it was only that first time and not the rest (which i do believe it can be because of my personalized http error messages in my server).

Later i saw an email saying that a user was locked out after too many login attempts. I noticed that ip was mine. I checked my wordfence setup and saw that i set up that it should blocked ips after 2 failed login attempts. And I did mistype my password a couple of times. I saw my ip listed in the blocked ips and removed it and now im able to login/out without problems.

So this is fixed. I think what confused me is the fact that i kept seeing those 200 status on the live traffic vs the 503 that appeared on the access log.

Mystery solved and wordfence is still up and running (and working just fine!).