plugin deactivated itself

Hi, I installed this plugin because of all the brute force attacks my website was getting. I use Wordfence security. I hid my wp-login.php page and gave it a new name. Then I set my Wordfence oprions to lock out anyone attempting to access wp-login.php. All worked really well until today when I went to update 2 plugins that Wordfence notified were in need – not WPS Hide Login – but when I attempted to login I got “page not found” trying some backwards attempts I was locked out of my own site by Wordfence so I had to get them to unlock all so I could get in. I discovered that WPS Hide Login was deactivated. I had not been in the backend for a few days and all was fine then. I checked the traffic logs and no one else had been in either. The only conclusion is that something caused the plugin to deactivate. The only plugin that self-updates is Wordfence and it had updated so I’m guessing that this had something to do with it. Is this a known thing? I’m afraid to set options to lock out attempts to access wp-login.php now in case it happens again – this is a problem because the hackers are really after this site for some reason (what’s up with that anyway?)

• This topic was modified 8 years, 1 month ago by esp2013.