Hi, how did you determine that that was this plugin? It sounds like something else, since the plugin doesn’t have any code to issue 404 codes under any circumstances…. and, by definition, a de-activated plugin can do nothing, because WordPress will never access it. IF something happens when a plugin is inactive, that’s definitive proof that it is related to something else.
If you click on the FAQ link on the right of this page, there’s an FAQ on disabling the plugin. But as I say, it sounds like something else, if you’ve already disabled it.
Thread Starter
SVTX
(@svtx)
Well I cannot login at all with this plugin activated so there’s definitely something wrong. It’s been acting up, told me I used the wrong code when it didn’t even offer to enter it so yeah, there goes that flawlessness.
Hi,
What versions do you have installed? The description of it complaining about a wrong code when it didn’t ask for one matches a problem that was fixed in the most recent release (this was with people visiting the login form when already logged in… it didn’t ask them for a code, and then complained about no code).
David
Thread Starter
SVTX
(@svtx)
I’m running version 1.2.21
Just tell me how to purge this plugin without Dashboard access. Like where does it write into the DB? Looks like I’m gonna have to do open heart surgery here.
Hmmm, strange. What kind of login form are you using? Is it from some other plugin (i.e. not the standard WP one)? Cached somewhere?
404 errors tend to come from security plugins that change the login process to be non-standard, or from mod_security on the webserver that blocks traffic it considers suspicious.
If you just rename wp-content/plugins/two-factor-authentication to anything else and go to your dashboard, then the plugin is completely gone, and if you still get a 404, it’s definitely something else. (Note that your front-end will not be reachable after removing that dir until you log into your dashboard , unless/until you name it back).
