B13story
Forum Replies Created
-
Thanks for the reply dwinden,
I see that all the options mentioned above are checked but I discovered something strange in the “Enable ban users” there are many blocked IPs they seem to be imported from .htaccess and not banned by the plugin.
To mention that my hosting provider has its own system that auto bans IP too and they are saved in the .htaccess so how could iThemes Sec work alongside with this system and write to the same list?!Yes only when you Block IP manually you can see it blocked otherwise no records in lockouts page.
Weird isn’t it?Thank you Stingray, great to hear that it worked well for you.
I will talk to the team and see what we can do for the moment, I hope to see a new update for WF soon.You should consider disabling XMLRPC if you don’t use it and add a captcha to your login page.
That worked for me.
Good luck !I had the same issue from a while but I fixed it by changing it in the options page.
Thanks for the contribution Stingray!
I’m not going to change anything in WF core files until they update it because I still use XMLRPC on my site for the Mobile App so I’m not sure if doing this will not cause any issues or maybe damages.WFMattR Great News Thanks!
Btw WFSupport, I just found out that scans are starting remotely rather than internally while the “start scans remotely” option is unchecked as you can see from the screenshots given above.
Does WF changes this option automatically when something goes wrong even if the option is kept unchecked or the options changes are not being saved?Also I agree with Stingray!
Please add the ability to block xmlrpc brute force attacks.Hi WFSupport
I don’t know exactly which options you want but here’s the full options page.
http://img11.hostingpics.net/pics/393637331.png
http://img11.hostingpics.net/pics/804202322.png
http://img11.hostingpics.net/pics/547723473.png
http://img11.hostingpics.net/pics/836000834.png
http://img11.hostingpics.net/pics/147447415.png
Thank You !Thanks for the reply
And yes the word was confusing but at least I don’t see the IP gets blocked after several lockouts.
If you could correct the misleading word and add the ability to permanently ban who login with “admin” rather than lockout that would be great!
Thank youThanks for the reply.
I tried to enable Javascript Console on the scan page but no errors were found.
Also the last scan as I can see has finished successfuly since an hour ago which I think it was not finishing yesterday because of the last update you made (btw even before update scans sometime doesn’t finish).
Again I see in the logs that someone probably a botnet is accessing admin-ajax.php too frequently which I think has a relation with the issue that caused WF to never finish/start scans.
Anyway, I’m still unable to get WF to block IPs/brute forcers automatically.Forum: Networking WordPress
In reply to: Manual WP update for multisite?You can make a backup of all your sites including database and then try the WordPress automatic update and if something goes wrong (which is not always the case) you can roll back to previous version by extracting your backup to your WP installation directory.
Otherwise you can do the opposite, extract the new WP version and override it with old one in the same directory (folder).
Note: deactivate all plugins before manually updating WP as they may cause problems after a “huge” update.
Good luck!Forum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] KeyloggersTry malwarebytes for your computer it is always up to date and works fine against all malwares including keyloggers.
There’s no hacker it is only an automated bot that tries to login and identify your username.
From what you’ve said above I think the bot figured out your username from the domain you use, most people’s usernames are same as their domain names for example: silky.com site would have a username “silky”.
You said WF doesn’t send any notif emails so in this case try using an SMTP (email) plugin and see if that works.
