404 Detection – Reoccurrence Blacklisted IPs

  • Resolved rebornhairppp

    (@rebornhairppp)


    7 years, 3 months ago

    Hello guys,

    It’s me again. Sorry to bother you but I am facing another problem.

    My 404 detection feature seems to be displaying ongoing event logs even for blacklisted IPs. For example, IP address 93.174.93.71 has been blacklisted a couple of days ago but that address is still showing up in my event logs as of today. It seems like this IP address is still trying to continue to access an attempted URL that’s forbidden even though it’s blacklisted.

    Two other observations. When I export the 404 event logs to CSV the Locked Status column doesn’t indicate “blacklisted” for any IP address I blacklisted. It’s a blank column with no fields. However, in WordPress, when I click on the 404 detection tab for your plugin, the Locked Status shows “blacklisted” for any blacklisted IP address.

    Another observation is when I click on the plugin’s dashboard and then the Permanent Block List tab nothing shows up. However, when I click on the Blacklist Manager feature, it shows a list of all the IP addresses I blacklisted on the 404 Detection tab.

    By the way, the Completely Block Access To XMLRPC feature is enabled.

    Any help would be more than appreciated!

    Thanks!

Viewing 4 replies - 16 through 19 (of 19 total)
  • Plugin Contributor wpsolutions

    (@wpsolutions)

    Thanks guys for your feedback.
    Using this info will help me to formulate a better solution for the case where blacklist and 6G are simultaneously active.

    Thread Starter rebornhairppp

    (@rebornhairppp)

    @wasca – Thank you again. That’s what I exactly did! ??

    @wpsolutions – I did a test run by removing the Require All Granted syntax from the .htaccess file while enabling 6G and 404 detection. The good news: I only see NEW IP addresses in my 404 Event Log. The bad news: as soon as I blacklist those NEW IP addresses, the Require All Granted syntax gets automatically added in my .htaccess file under the Apache >= 2.3 section.

    As such, I have to manually jump into the .htaccess file and remove that syntax. I have to manually perform this step each time I blacklist a NEW IP address given that both the 6G firewall and 404 detection features are ENABLED!

    Do either of you have recommendations to automate the process of removing the problematic syntax every time a NEW IP address is blacklisted?

    Thank you again, wpsolutions and Wasca for your utmost assistance and kind diligence. My monetary support was well spent for your plugin.

    As a warm reminder, @wpsolutions, if you can be so kind to keep me under your radar (I know you have mountain of users and requests you need to attend to) about any updates on when your plugin will support public IPv6 address I would be graciously thankful!

    Take care like always and God Bless you too for a job well done!

    Thread Starter rebornhairppp

    (@rebornhairppp)

    @wpsolutions – One other thing I forgot to mention and I think it’s quite important. If you can add this on your to do list to incorporate in future updates that would be incredible!

    I noticed blacklisting IP addresses under 404 event logs can be extremely laborious if there are many different IPs appearing on multiple pages. I just cleared my event logs three days ago, and I already have 11 pages of new IPs which I need to blacklist. The problem is the bulk action option to blacklist the IPs are page-specific meaning I have to click on the next page to blacklist any new IPs not appearing on page 1, or 2, or 3…

    Would there be a way to permanently or temporarily with a click of a blacklist or temp block button block ALL IPs appearing on multiple event log pages similar to the delete all 404 event logs button?

    Thanks wpsolutions again!

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Hi @rebornhairppp,

    as soon as I blacklist those NEW IP addresses, the Require All Granted syntax gets automatically added in my .htaccess file under the Apache >= 2.3 section.

    This will not be an issue in the next release because I have implemented a fix for that.

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘404 Detection – Reoccurrence Blacklisted IPs’ is closed to new replies.