Solutions to access your wp-admin when user locked out!!

There are 4 solutions to access your wp-admin when user locked out!!

  1. Bhawani Singh
    This article will show “How to get back into WordPress dashboard when we are currently locked out of WordPress”. It will really disappointing when you are not able to access your own WordPress website.

    We might have a backup to our website but there are few steps to make our situation better. Here we learn about scenarios that will result in locked, the scenarios are the future use and for the few who are already locked out, there are solutions available. Just relax this locked out of WordPress is actually pretty reversible.

    Scenarios and solutions:

    There are some commonly found scenarios given here, check these scenarios for future reference:
    1. Too Many Login Attempts
    2. Admin Privileges Lost
    3. The Dreaded White Screen of Death
    4. A PHP Parse Error
    • Too Many Login Attempts:

    Logging in to your WordPress for several numbers of times can cause a lock out, this usually happens accidently that is when a user manages multiple sites it can be a difficult task to remember every single password. The solution is to disable lock out option in your database.

    Solution:

    1. You can easily unlock your user through database by using PHpMyAdmin. If you are using ithemes security plugin then you can find “wp_itsec_lockouts” table in database and unlock your user by deleting the row of the table.

    lock.png

    2. If the above solution won’t work then next solution is to disable the security plugin from “wp-content” folder for some time by changing the name of the “Plugin” folder. And then it will get rectified automatically.

    plugins.png
    • Admin Privileges Lost:
    If someone hacks your site, they might also remove your admin privileges. You can log into WordPress but there is no access to the important menus like Plugins and Themes.

    The solution is very simple:

    Step 1: Create a new user and required fields are a new ID, user_login, user_pass, user_nicename, user_email, user_register, user_displayname and user_name.

    newuser.png

    Step 2: Save everything and configure the user metadata using unmeta_id, user_id, meta_key, meta_value.

    usermeta.png

    Step 3: Save the above, enter into WordPress and edit your profile.

    Step 4: After this, just deal with the potential hackers with professionals.
    • The Dreaded White Screen of Death:
    If you have a plain white screen when you login to WordPress then you may be experiencing The Dreaded White Screen of Death issue. The result of this issues no data only a white screen. The login page is white in color and nothing else. The reasons are less memory limit of your WordPress (update your core memory), faulty login can also cause white screen, faulty theme is also a reason. If you need more information about the white screen on wordpress website then you can check this article: How to fix "Wordpress white screen of death" ?

    Solution:
    1. The perfect solution is to deactivate the plugin. Re-do the plugin name and activate it step by step.
    2. If the deactivation of plugin is wont work for your website then it may be possible that theme is causing the issue. Deactivate the current theme by renaming the folder of plugin and then check.
    3. Try to increase the limit of the memory sometimes it may be insufficient.
    • A PHP Parse Error:
    parseerror.png
    If you find yourself locked out of your WordPress site with a screen showing a error message, it is actually due to inserting a code of wrong snippet in any of your files. The beginners generally use the built-in WordPress editor to do so they are victims of such parse errors. This can also be solved, just try to remember where you inserted your snippet, simply connect to your web site through FTP and edit with code editors like notepad++ and remove the particular snippet.

    Solution:

    If you are getting parse error on your wordpress website, it may be possible that your changes in functions.php file are causing the issue. So it’s better to revert back the changes in your functions.php file via FTP.