New to the community? Start here

Issue with Defender 404 Lockouts and Notifications

I’m getting lots of 404 notifications from my sites’s localhost IP. I’m concerned

Thu, 26 Nov 2020 23:38:47
More The Hub discussions
The Hub
  • Nithin Ramdas
    • Support Wizard

    Hi Jackson ,

    We are able to replicate the lockout regarding the IP 127.0.0.1 and have already reported this to our Defender teams attention. Our team is already working on a fix regarding this in the next update.

    Could we know whether Preload cache in Hummingbird was activated during the time the issue was noticed? I could notice its currently disabled, but one of the reasons for the issue to occur was due to that.

    Could I know are you still getting notifications even its the notifications are disabled in Defender side? So that we could check further regarding this if needed.

    Sorry for any inconvenience due to this.

    Kind Regards,
    Nithin

  • Jackson
    • Trying to stay calm

    Hi Nithin,

    Thanks for the update. Preload cache is usually activated for speed improvements – so I’m not sure why it was disabled at the moment. However, I did not make any changes to it in the last couple of days so I expect it was disabled.

    Notifications: Not anymore; my support agent suggested enabled notifications > choose user > remove my account > disable notifications again.

    Even tho notifications were all disabled, I was getting hundreds (400+) emails for every single lockout. It seems that the individual 404 lockout notifications do not inherit the parent settings.

    What’s concerning is that setting a block on the localhost IP and the path /author/ had no impact on the attack.

    Thanks

  • Nebu John
    • FLS

    Hi Jackson ,

    Even tho notifications were all disabled, I was getting hundreds (400+) emails for every single lockout. It seems that the individual 404 lockout notifications do not inherit the parent settings.

What’s concerning is that setting a block on the localhost IP and the path /author/ had no impact on the attack.

    Our developers are already aware of it and are looking into it to identify the cause and release a fix as fast as possible. Unfortunately, we do not have a workaround for this right now.

    Please make sure to keep the plugin up to date as our Defender developers are working on it to get it sorted out soon. I am extremely sorry about the inconvenience caused by this.

    Kind Regards,
    Nebu John