Nettric

I changed everything back to default after I uninstalled the plugin. Not going to worry about it right now.

I appreciate all the time you’ve spent on trying to resolve this.

I reinstalled the plugin, selected a different permalink format, saved the configuration and still the same behavior.

No worries at the moment. There’s something strange as how IIS handles these that I can’t put my finger on as when I try to access my new login path, it still throws server-side 404s.

I wish I could help further. I’m a network enginner and IT Manager…not a programmer ?? It really is a mystery. I assume you’re testing with Apache on Linux?

Funny thing is, when activated and I try to access the original /wp-login.php I get a 404 that is formatted with my WordPress theme. The file is still physically there in the root of my WP site. So WordPress is catching it based on the URL and behaving properly in that scenario…giving me a 404 when I try to access wp-login.php.

Yet when I try to access my new login location at /mylogin, I get a server-side 404…so WP doesn’t seem to be catching the 404 and leaves it up to IIS to serve up the error pages. The directory isn’t physically there so my server-side 404 pops up.

Sorry, same thing: server-side 404 (I get my custom 404 page). I even reset the error pages back to IIS defaults and still get a server-side 404 (non-WordPress formatted 404)

No worries.

My thoughts:

When activated, the 404 comes across as a WordPress formatted 404. Like WordPress is saying that the page should be there but a link is broken.

My custom 404 happens when the file or directory doesn’t exist at all. At that point, IIS…not WordPress…throws my custom 404. The custom 404 is configured in IIS and simply points to my custom static pages.

That is a custom server-side 404…Independent of wordpress.

The custom 404 you see is my custom 404. Even with the default IIS 404 http error page, it doesn’t give much information.

Even though IIS works a bit differently than Apache on Linux and hardening IIS and the anonymous IUSR account IIS uses for visitors, that really shouldn’t be an issue since this plugin is a simple update to the DB…

In other words, even though you login with a local WP account, all folders and file NTFS permissions are still being assessed with the IUSR account and NOT the account you log into WP with. But again, being as the plugin simply updates a MySQL value, this shouldn’t be the issue.

Let me know when you have time to work on it and I can give you access in the name of helping you improve the plugin. Do you just need WordPress Access or do you need/want server access as well?

I would prefer we exchange that info via email. You can email me here:

Please write my email address down as I will delete it here in a few minutes…

Literally just mylogin. I have just installed the plugin via the plugin manager, activated the plugin, kept the default “login” path in Permalinks, saved the config, and still get a 404.

Here is my website: https://www.giantpythons.com
This should be the new login: https://www.giantpythons.com/login

You’ll see a custom 404 pop up…

In the textbox, I simply erased the default login and typed mylogin with no forward slashes anywhere.