Install/Config Hide Backend Forbidden 403 error
Installation of Better WP Security (BWS) onto 275 sites. 170 sites complete. All sites substantially same structure offering different content (WP, Framework, Theme, & 13 Plugins the same).
5 sites experience 403 Forbidden (You do not have permission to access this document). Problem presents upon logging out of site after BWS installation/configuration. Same message presents when attempting to access backend. Suspect Hide Backend feature as this is the first time I have used the feature on a large number of sites.
Compared .htaccess file contents between three sites: Broken, working with feature, and working without feature. Able to identify the block of commands associated with the feature. In my case these are the last 25 lines (including blank lines) begining with a RewriteRule which contains my login address and ending with a RewriteRule which contains …wp-login.php?…. The last line is just before “# END Better WP Security”.
I commented out this portion of the .htaccess (‘# ‘ used to comment). Changed the file readonly status to allow writing. Saved the result.
I was then able to login to the site using /wp-login.php.
I re-tried the original Hide Backend configuration and site access became forbidden. In retrospect it was interesting to note that the key generated was the same.
I tried the original Hide Backend – this time checking the generate new key. This time the feature work as expected.
I’m not able to figure out why one key works and another does not.
Comment out the Hide Backend code within .htaccess (not labeled – see notes above to locate). Change the read/write status of the file and save.
Open site with /wp-login.php. On the Security/Hide Backend page check the Generate New Secret Key option and save.
Logout/login to test.
I hope that this helps anyone encountering this problem. If I were not working with such a large number of sites I would not have uncovered it or be able to resolve the problem.
- The topic ‘Install/Config Hide Backend Forbidden 403 error’ is closed to new replies.