• Hi. I upgraded to version 4.5.6 of iThemes security, and I can no longer access /wp-admin.

    I have hidden the backend, to /wplogin, but after I login, the admin bar on the front end is not visible, and /wp-admin produces a 404.

    The only way I can circumvent this is to rename /wp-content/plugins/better-wp-security to /wp-content/plugins/better-wp-security2

    https://www.ads-software.com/plugins/better-wp-security/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hello, I am also having the same issue after upgrade.

    I am neither able to login to admin page from both wp-admin or my change /wpadminlogin.

    could someone please help.

    Rename the plugin in the /plugins folder in your Cpanel. It’ll deactivate it.

    Then try a fresh install maybe?

    I get this too. It works fine for a few days then suddenly one morning all I get is 404 Not Found for any page in the wp-admin folder so I cannot get at the login page or the dashboard to administer the site. It must think I’m some sort of intruder and locks me out. However, there is no message on the iThemes log except a report of the 404 for the requested page (eg the login page).

    I have two WP subwebs, one of which is a private testing site and the other is ‘live’ and linked to from my main (non-WP) site. What’s interesting is that the test site is completely unaffected – it’s only the live site that has this problem. Both have iThemes 4.5.6 and it’s set up pretty-much identically on both sites.

    The only way to bring it back to life is to rename the plugin, log in, rename it back and re-activate iThemes. I got that solution after posting this problem on the general WP Forum as at that time I didn’t know it was iThemes-related. If anyone on here has more-specialised knowledge about these things, I’d be happy to hear from them.

    I’m not convinced deleting and reinstalling it would fix things, but would probably be persuadable if it was guaranteed to to work. Is it possible to retain all the Settings when doing that?

    Running WP 4.1 (although this started under 4.0.1) under the Weaver II theme.

    Further to my post just above, I found today that my secondary test system was affected for the first time as well as my live site. I went into the usual recovery method and found on reactivating iThemes on the live site that it couldn’t find the plugin directory. I faffed about for a bit, panicking slightly, until I found that the reactivation was attempting to use the name of the temporarily renamed directory (now renamed back to its proper name) so failed. I renamed it back to the temporary name, and it reactivated ok. Phew.

    I did the renaming thing on the testing site and it reactivated normally. I decided that I didn’t want the iThemes in my live site to remain in a directory with a non-standard name, so I deactivated it, deleted it and reinstalled it. I then manually reset all the settings using those from the test site.

    The question is, how did WordPress (or iThemes) know that I had renamed the plugin directory completely outside the WP environment (using my standalone FTP product) and start using that name in the pathname for the activation process? And why didn’t it similarly use the right name when it was renamed back? I’m confused.

    I hope the fresh install will cure this issue, but I’m not holding my breath.

    I had this problem too, I got a 404 page when I tried to log into the wordpress admin page. I fixed it in the Hide Login area. the login slug changes the web address to log in. Just copy that address and I was able to log in again. Even the default wp-login changed the default page name wp-login.php. this fixed it for me. If you have 404 on other pages, it might be a hacker, good luck, hope you fix it. ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘can't login to wp-admin’ is closed to new replies.