While the home page is inaccessible, all other pages ARE accessible.
Detail:
? We have an external monitor that loads the home page and scans for a block of text. If the text can not be loaded it will email an alert
? We will then have humans check the home page from different locations and IP addresses. All users will confirm that the home page is redirecting to 127.0.0.1.
? This problem persists between 10 minutes and an hour, then goes away on its own
The site gets enough traffic to need caching and this is acting like a situation where one bad actor triggers the 127 redirect, and it then gets cached and served to the public until the cache naturally clears.
The login page has been moved from the default location
What doesn’t make sense:
? Cookie-based brute force protection is NOT enabled
? All of the reports in this forum state that this 127′ redirect only happens on the LOGIN page, not the website home page (which does not have a login form or link)
There are no other security plugins installed and active.
Thanks and let us know.
]]>The original topic I opened about three weeks ago cannot be found either in the chronological listing, or via search, and I have no idea why. Repeated follow-up posts, some with new information, are not being responded to. I hate having to create a new Topic just to link back to the original thread, but this is an unusual (and urgent) circumstance.
Given that my issue involves the failure of some pretty essential core WF functionality (IP identification and blocking), I would hope that the many users who have identified this issue can get a response soon.
Thanks in advance.
]]>Is there *ANY* way to have this traffic more accurately identified? Mark Maunder’s post from 2015 announcing Wordfence’s IPv6 capabilities made specific mention of the ability to look up PTR records, and do fairly robust geo-location as well.
Has something become broken in the code, or is this a misconfiguration issue in my Wordfence plugins (which are all standardized on a template through Wordfence Central, btw), or perhaps a misconfiguration issue on my web hosting company’s server?
Screenshot attached to show example of what I’m seeing in Live Traffic:
Thanks in advance for any advice/suggestions you may have!
]]>I am suddenly unable to access my site’s login page; I am getting the dreaded 127.0.0.1 loopback. I have made no changes to AIOS since a few days ago and everything was fine before. I am able to get in if I disable AIOS via SFTP, but activating the plugin either via the admin page or SFTP leads back to 127.0.0.1, so I can’t even access the AIOS options.
I’m guessing there’s an issue with the cookie-based brute force prevention, since I have that active in my AIOS settings, but with no way to access the settings due to the loopback issue, I can’t disable it. Please provide a fix/workaround for this urgent issue!
]]>as soon as I download AIOS and click on “activate” I land on the 127.0.0.1 redirect. The only way to regain access to my dashboard is to delete or rename the plugin. So I haven’t made any settings yet with which I could lock myself out. What can I do?
Thanks in advance
Seli
]]>