Title: Enable Hide Backend &amp; Google authenticator
Last modified: August 21, 2016

---

# Enable Hide Backend & Google authenticator

 *  Resolved [PE-Pernet](https://wordpress.org/support/users/pe-pernet/)
 * (@pe-pernet)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/)
 * Hi,
    I use Google authenticator to secure my login but, because I’m facing a 
   lot of lockout due to bad login, I’ve try to enable “Hide backend” feature. It
   works… but I’m no longer requested to enter my Google authenticator code ! Yo
   be honest I was so happy not to be locked out that I disable this feature before
   something went wrong ! Why do I land on different login page when I activate 
   this option ?
 * [https://wordpress.org/plugins/better-wp-security/](https://wordpress.org/plugins/better-wp-security/)

Viewing 15 replies - 1 through 15 (of 18 total)

1 [2](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/page/2/?output_format=md)

 *  [Nando_lavras](https://wordpress.org/support/users/nando_lavras/)
 * (@nando_lavras)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767230)
 * Same problem, when hide backend is enabled the google auth plugin not work at
   all…..
 *  [upfromheree](https://wordpress.org/support/users/upfromheree/)
 * (@upfromheree)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767234)
 * I had the same issue with Google Authenticator, though I wasn’t able to log in
   at all. I had to rename the plugin folder to break it so I could.
 *  [Nando_lavras](https://wordpress.org/support/users/nando_lavras/)
 * (@nando_lavras)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767235)
 * For me even with G Auth enabled i able to login normally only with user and password….
   It’s really bad, i really need this fixed.
 *  Thread Starter [PE-Pernet](https://wordpress.org/support/users/pe-pernet/)
 * (@pe-pernet)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767236)
 * Agree !
    That would add an additional layer of security to the product.
 *  [Nando_lavras](https://wordpress.org/support/users/nando_lavras/)
 * (@nando_lavras)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767240)
 * 4.0.12 up…. G Auth issue continues!
 *  [capotea](https://wordpress.org/support/users/capotea/)
 * (@capotea)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767258)
 * Same problem!
 *  [Nando_lavras](https://wordpress.org/support/users/nando_lavras/)
 * (@nando_lavras)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767262)
 * 4.0.16 up…. Nothing solved!
 *  [capotea](https://wordpress.org/support/users/capotea/)
 * (@capotea)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767277)
 * 4.0.19 … not solved
 *  [Stephen](https://wordpress.org/support/users/stephenjudge/)
 * (@stephenjudge)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767283)
 * Prior to the re-write from Better-WP-Security to iThemes Security, I had both
   the ‘Hide Backend’ feature of B-WP-S enabled and the Google Authenticator plugin
   installed and both worked fine. After the re-write to iThemes Security I continue
   to have the ‘Hide Backend’ feature enabled but now the Google Authenticator plugin
   won’t work. It’s a tough choice between choosing which feature I want to work
   the most. I am very uncomfortable with not having the 2FA of the Google Authenticator
   plugin working after having it in place for so long.
 * I also 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.
 *  Plugin Author [iThemes](https://wordpress.org/support/users/ithemes/)
 * (@ithemes)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767284)
 * Hey All,
 * This is being addressed. Could you please update to v4.0.21 and see if that helps?
 * Thanks,
 * Gerroald
 *  [Nando_lavras](https://wordpress.org/support/users/nando_lavras/)
 * (@nando_lavras)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767285)
 * Hi iThemes, i’ve updated to 4.0.21, nothing changed…. The G Auth continues not
   working….
 * Thanks in advance.
 * PS: For information, i’m using the WP Google Authenticator v1.0.7 plugin, but
   i already tested with Google Authenticator plugin (other plugin that works in
   version 3.6.6) and this plugin not works too.
 *  [Stephen](https://wordpress.org/support/users/stephenjudge/)
 * (@stephenjudge)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767286)
 * I have updated to iThemes Security 4.0.21 and I am using Google Authenticator
   0.47 ([http://wordpress.org/plugins/google-authenticator/](http://wordpress.org/plugins/google-authenticator/))
   on WordPress 3.8.2. The problem still exits, the Google Authenticator plugin 
   is still broken.
 * Are some some specific settings in iThemes Security we should toggle on or of?
   Please advice.
 *  [capotea](https://wordpress.org/support/users/capotea/)
 * (@capotea)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767289)
 * The update didn’t help for me.
 *  [fridha](https://wordpress.org/support/users/fridha/)
 * (@fridha)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767291)
 * Really need this fix. I downgraded for now.
    Google Auth also important for me.
 *  [Stephen](https://wordpress.org/support/users/stephenjudge/)
 * (@stephenjudge)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/#post-4767294)
 * It looks like your 4.0.23 update of iThemes Security has fixed the problem with
   the 2FA Google Authenticator plugin. Mine is back working again. Thanks for this
   fix and I apologise for suggesting above that you may have no incentive to fix
   this as you plan to introduce 2FA as a Pro feature for iThemes Security, you 
   have proved me wrong and I am glad so.

Viewing 15 replies - 1 through 15 (of 18 total)

1 [2](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/page/2/?output_format=md)

The topic ‘Enable Hide Backend & Google authenticator’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

## Tags

 * [hide backend](https://wordpress.org/support/topic-tag/hide-backend/)

 * 18 replies
 * 8 participants
 * Last reply from: [iThemes Support](https://wordpress.org/support/users/ithemes-support/)
 * Last activity: [12 years, 1 month ago](https://wordpress.org/support/topic/enable-hide-backend-google-authenticator/page/2/#post-4767307)
 * Status: resolved