Hide backend not working

Did you allowed the plugin to write .htaccess file? … In global settings
I have

• This reply was modified 5 years, 10 months ago by shalke04.

Hi,
i have..

I am using nginx server so there is rewrite on nginx.conf instead.

Can anyone help?

As of the 6.3.0 release the iTSec plugin Hide Backend feature does not write to the .htaccess or nginx.conf conf files. Any present rewrite rules in the nginx.conf (or .htaccess) file are the result of other iTSec plugin features.

When you enable the Hide Backend module an email notification is send to the site admin(s). Check the email and make sure you are using the correct login slug.

Hi all, seems i have an issue similare here:
when i activate the hidden backend module, it does not activate my new admin adress…

I am using nginx and it is a fresh install.
I checked file rights and ithemes sec can write the nginx.conf
Tryied a lots of solutions but found no true solution/advices on the web.
So to be clear:when i try my new admin adress https://mysite/mynewadmin for exemple i have an error 404. BUT i can log in with the https://mysite/wp-login.php so it seems that nothing happened.

I test a nginx specific directive in the server:

if (!-e $request_filename) {
set $test P;
}
if ($uri !~ ^/(plesk-stat|webstat|webstat-ssl|ftpstat|anon_ftpstat|awstats-icon|internal-nginx-static-location)) {
set $test "${test}C";
}
if ($test = PC) {
rewrite ^/(.*)$ /index.php?$1;
}

and it made my new adress working…but also /wp-login.php and /admin! (as the normal hidden module activated should exclude /wp-login.php and /admin)

Any help here to understand?
Thx a lot!

• This reply was modified 5 years, 9 months ago by KaizenLab.