Version 4.0.7 is live. Please let us know if you are still seeing issues

I’m just a member here but – changing the name of the plugin via ftp worked for me to let me back in and it seems for others above. Other notes above will provide guidance on what you might want to do beyond that.

Thanks, jimii! I will probably wind up doing that…but I was hoping to be able to keep using the plugin. Gracias.

Quantaweb – i plan or hope to keep using it as well – but just waiting for the fix : )

Don’t know about the rest of you but I’m either going to ditch the new version and roll back to a previous one, or completely all together. I’m still debating this.

Why ceased to answer in url /wp-admin/ with an error 404 in a version 4.0.16?

this is total bullshit! I updated the plugin and now I have no access to my site either by standard wp-admin or the custom URL. Both are returning 404 error.

I have even deleted DB and went with new install. Result? Same shit.

I was actually forced to delete this plugin on my own website, but what is more important most of my clients now have the same issue and who are they blaming for this? ME!

THANKS A LOT!!!!

If you revert back to an old version of the plugin, you will have access to your admin. I had to reset the settings in the plugin, but am now able to log into the admin screen.

I am using version 3.6.6 as the one that works.

Hmm, now we are up to version 4.0.16. This version is another failed attempt to fix the problems that surfaced in 4.0.7. People continue to have issues.

This means that the folks at iThemes have tried NINE TIMES to fix this problem and are still failing.

Have you ever know a competent software company to release NINE bugs fixes and each any everyone of them FAIL !!!

What’s worse is their silence.

@waldenponddesign, how about this company – Microsoft?

I found a solution to my problem in case it helps!

For me this latest version (4.0.16) was still locking me out as soon as I activated the “Hide Login Area” and logged out and back in with the correct new admin link.

So I tried disabling the “Root Relative URLs” plugin by Marcus E. Pope and PRESTO! the administrative login link now works just fine!

SO NOTE TO iThemes Security people, please be aware that your plugin is 100% INCOMPATIBLE with “Root Relative URLs”, and vice versa!

This incompatibility did not exist with the older “Better WP Security” plugin.

ALSO: Please make sure you are logging in with a link that does NOT HAVE A TRAILING FORWARD SLASH!!! That will NOT WORK!

E.g.

"https://mydomain.com/my-login/"  <--WILL NOT WORK
"https://mydomain.com/my-login"   <--WORKS!

I’m having issues with Cart66 Lite – ajax function to add items to cart does not work Ithemes Security enabled. I tried turning off the Hide Backend – no effect. Also clicked the box for issues with themes, did not fix the problem.

To CarrieM and others,

I followed the suggestion of CarrieM and deleted .htaccess. But oh my, there were 2 .htaccess files in my database files, and I did not know so I, clever me, deleted the wrong one. Still no eccess. So I had to delete the other one too, it read: deny from all.
Still no access!
Then I found a .htaccess text on some forum, it read:
# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Now I could enter my site again, and I hope will be in the future as Ithemes Security asked to change files and I gave permission. so for the future… I do not know what other problems I will meet.

I’m seeing this warning error on 404 pages:

Warning: in_array() expects parameter 2 to be array, string given in /home/x/public_html/wp-content/plugins/better-wp-security/modules/free/four-oh-four/class-itsec-four-oh-four.php on line 32

On the issue for the broken Google Authentication plugin as a result of the Better-WP-Security re-write to iThemes Security, I noticed that iThemes are planning their own 2FA Authentication feature as a pro feature for iThemes Securiy, so maybe they have no incentive to fixing this Google Authenticator bug they have introduced.

Dang, I didn’t realize it was iThemes that was breaking Google Authentication. I liked iThemes, but I have to disable it until this is fixed.