Title: Hide Backend error 404
Last modified: April 18, 2022

---

# Hide Backend error 404

 *  [timmer81](https://wordpress.org/support/users/timmer81/)
 * (@timmer81)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/)
 * I am using ithemes security 7.1.1 and am having a problem with the hide back 
   end feature.
 * The unique login is not working and nor is the normal /folder/wp-login.php.
 * However, when a itsec token is used to log in it works??
 * I have deactivated plugins to see if there is a conflict but there doesn’t appear
   to be.
 * Please could someone point me in the right direction to try and solve the issue?

Viewing 10 replies - 1 through 10 (of 10 total)

 *  [mikes9](https://wordpress.org/support/users/mikes9/)
 * (@mikes9)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15569063)
 * Could it be fixed?
 *  Thread Starter [timmer81](https://wordpress.org/support/users/timmer81/)
 * (@timmer81)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15569911)
 * Hi [@mikes9](https://wordpress.org/support/users/mikes9/)
 * It doesn’t work with my chosen url sadly.
 * Not really sure what else to try
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15569990)
 * Hi timmer81,
 * > However, when a itsec token is used to log in it works??
 * Can you explain this a bit more. Use an example.
 * +++++ To prevent any confusion, I’m not iThemes +++++
 *  Thread Starter [timmer81](https://wordpress.org/support/users/timmer81/)
 * (@timmer81)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15570031)
 * from what i understand this was a change in a previous update
 * > `Important: The way that Hide Backend functions changes in this release. Previously,
   > if your Hide Backend Login Slug was wplogin, going to example.com/wplogin would
   > result in the URL remaining example.com/wplogin. The new implementation of 
   > this feature results in a redirect to a URL that looks as follows: example.
   > com/wp-login.php?itsec-hb-token=wplogin. While this may not be desireable for
   > some users, this change was necessary to fix longstanding compatibility issues
   > with other plugins. Once you access the login page using the Login Slug page,
   > a cookie is set with an expiration time of one hour. As long as the cookie 
   > remains, you can access example.com/wp-login.php without having to access the
   > Hide Backend Login Slug first. If you wish to confirm that Hide Backend is 
   > working properly on your site, opening up a private browsing window is a quick
   > way to test without having to log out and clear cookies.`
 * But for whatever reason when I login with example.com/shop/examplelogin it doesn’t
   work
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15570183)
 * Yes, that is correct.
 * example.com/shop/examplelogin it doesn’t work = 404 ?
 * and
 * example.com/shop/wp-login.php doesn’t work = 404 ?
 * and
 * example.com/shop/wp-login.php?itsec-hb-token=examplelogin works ?
 * Based on the provided info so far, it looks like the hidden slug is not recognized
   and therefor there is no redirect taking place.
 * You are not using any special chars in the hidden slug ?
 *  Thread Starter [timmer81](https://wordpress.org/support/users/timmer81/)
 * (@timmer81)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15570361)
 * Hi [@nlpro](https://wordpress.org/support/users/nlpro/)
 * Thank you for your reply.
 * No special characters
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15570415)
 * Try and toggle the Hide Backend **Enable Redirection** setting on/off (if not
   already tried), to see whether that makes any difference.
 *  Thread Starter [timmer81](https://wordpress.org/support/users/timmer81/)
 * (@timmer81)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-15572515)
 * Hi [@nlpro](https://wordpress.org/support/users/nlpro/)
 * Thank you for your reply.
 * I have tried that but sadly it did not make any difference
 *  [josegutierrez65](https://wordpress.org/support/users/josegutierrez65/)
 * (@josegutierrez65)
 * [3 years, 8 months ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-16019259)
 * I have the same issue, cannot fix it
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [3 years, 8 months ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-16019296)
 * Hi josegutierrez65,
 * Make sure permalinks are enabled for your site (Settings > Permalinks).
 * If your site is using permalinks try and reset the permalinks (if not already).

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Hide Backend error 404’ 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

 * [iThemes Security](https://wordpress.org/support/topic-tag/ithemes-security/)

 * 10 replies
 * 4 participants
 * Last reply from: [nlpro](https://wordpress.org/support/users/nlpro/)
 * Last activity: [3 years, 8 months ago](https://wordpress.org/support/topic/hide-backend-error-404/#post-16019296)
 * Status: not resolved