[Plugin: Hide Login] Tried on a Multisite Installation, No change

did you install wordpress at the root folder or at a sub-folder ? ( e.g. on a subdomain ) does your .htaccess file contain any other rules ?
there is no difference in use of this plugin on a single user wordpress blog or on a multi site one.

>did you install wordpress at the root folder or at a sub-folder ?

It’s a Root folder network .
Ex: Main site : mysite.com
Subsites : sub1.mysite.com , sub1.mysite.com

>does your .htaccess file contain any other rules ?

No ! I have tried on a fresh installation and also on another installation with no other rules

Any update with this issue? I am experience similar issue.

the generated .htaccess clearly shows the folder or blog that was generated by it.

Should this plugin be generated at the root level? or do you need to place each generated site login info into the .htaccess?

ex:

# HIDE-LOGIN
RewriteEngine On
RewriteBase /
RewriteRule ^foo-logout example/wp-login.php?action=logout&_wpnonce=78475b5ba8&hide_out_key=0adG0jNA [L]
RewriteRule ^foo-logout example_2/wp-login.php?action=logout&_wpnonce=78475b5ba8&hide_out_key=0adG0jNA [L]
RewriteRule ^foo-bar example/wp-login.php?hide_in_key=AJcAce0&redirect_to=https://blog.mysite.com/example/wp-admin/ [R,L]
RewriteRule ^foo-bar example_2/wp-login.php?hide_in_key=AJcAce0&redirect_to=https://blog.mysite.com/example_2/wp-admin/ [R,L]
RewriteRule ^foo-admin example/wp-admin/?hide_admin_key=LARa [R,L]
RewriteRule ^foo-admin example_2/wp-admin/?hide_admin_key=LARa [R,L]
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example/wp-admin
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example_2/wp-admin
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example/wp-login\.php
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example_2/wp-login\.php
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example/foo-bar
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example_2/foo-bar
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example/foo-admin
RewriteCond %{HTTP_REFERER} !^https://blog.mysite.com/example_2/foo-admin
RewriteCond %{QUERY_STRING} !^hide_in_key=AJcAce0
RewriteCond %{QUERY_STRING} !^hide_out_key=0adG0jNA
RewriteCond %{QUERY_STRING} !^hide_reg_key=AHyFz9nA
RewriteCond %{QUERY_STRING} !^hide_admin_key=LARa
RewriteRule ^wp-login\.php https://blog.mysite.com/example [L]
RewriteRule ^wp-login\.php https://blog.mysite.com/example_2 [L]
RewriteCond %{QUERY_STRING} ^loggedout=true
RewriteRule ^wp-login\.php https://blog.mysite.com/example [L]
RewriteRule ^wp-login\.php https://blog.mysite.com/example_2 [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END HIDE-LOGIN

@parswp

Please let me know if you need more details from me which may help to replicate the issue

Thanks

a new version of hide login plugin is just released.
but the support of wp multisite has been dropped.
According to this :

WordPress Multisite (aka. Network Site) differs from single instances and the fact that the .htaccess rules apply to the entire network, flushing the rules won’t re-generate the .htaccess file.

I am currently unaware of how to add custom .htaccess content/rules at this time since there doesn’t appear to be any built-in WordPress functions for this in Multisite mode.

Does the update still show the generated output? I have the ability to manually modify my .htaccess file.

I could use the plugin as a rule generator and perform a copy/paste. However, I have not had success with using this plugin on a multi site install. If I use the generated code, would/will this plugin work with a multisite? Or has it been re-written in such a way that it would/will only work with single instances?