How to Fix WordPress Keeps Logging Out Problem

How to Fix WordPress Keeps Logging Out Problem

One of the most frustrating problems for WordPress users is when the platform keeps logging you out when you are trying to make and/or save changes. This is also referred to as the WordPress session timeout issue. There are a variety of things which can cause this particular issue however they can all be addressed by following some basic troubleshooting procedures.

How to Fix WordPress Keeps Logging Out Problem

1. Deactivate Plugins

As with a majority of architecture related problems within the WordPress platform the first step is to deactivate any plug-ins you are using. If all of the plug-ins are deactivated and you are no longer seen this problem then it is safe to assume that one or more of the plug-ins is the cause. Reactivate each plug-in one at a time until you identify the culprit. Once you identify which one is causing the problem you can either simply find an alternative which offers the same functionality or you can tweak the code and fix whatever the specific issue is.

2. Empty Cache

If you are using a WordPress caching plugin then it could be causing the problem. You will notice the problem was fixed when you deactivate the plug-in however when you reactivated the old cache data will still be used. By simply emptying the cache or creating an updated cache the problem could be fixed.

3. Clear Browser Cookies

Another common solution is to simply empty your browser’s cache. The WordPress login system operates based upon session cookies. Sometimes an older or expired cookie could be overriding your recent login. This is not usually an issue with newer browsers but is simple to do so it is always worth checking.

4. Restore Website from Previous Backup (If Possible)

If you regularly create backups of your website (and you should be) then restoring your website from a previous backup may be a necessary solution. This is particularly true if deactivating and reactivating the plug-ins is not working. There is always a chance that a plug-in made a code change within the WordPress architecture which is now causing the problem. If restoring your website from a recent backup provides the solution then double check all of the recent changes you made to see which one could be causing the problem.

5. Check the Settings

A little-known solution has to do with the settings tab in the WordPress admin area. WordPress sets a cookie in your browser to authenticate a login session. This cookie stores information for the WordPress URL which you entered in your settings section. As a result, if you are accessing your website from a URL which does not match the one you entered in the WordPress settings then the platform will not be able to authenticate your session. Make sure that the WordPress address and site address are the same. In most cases, the problem is that www. is in one address bar but not the other. If you cannot log into your website at all then you may need to do this by editing the wp-config.php file via an FTP connection.

1 Comment
  • Freda J. Murry says:

    I have had this problem before and vendor tips very helpful. For me, deactivating plug-ins was what fix the problem. I then reactivated them one by one to identify the culprit. Unfortunately, it was a free plug-in and the developer was no longer supporting it so I had to find a different option. While the experience was frustrating it was a nice reminder to only use plug-ins that are actively supported, even if they are free.

    When I reactivated the plug-in and I didn’t have to empty my cache or clear my browser cookies. To be fair, I also didn’t reactivate the plug-in that was causing the problems. As I said the above I just switched plug-ins.

    I would hate to have to do a full website restoration from a previous backup to fix this problem. That would be incredibly frustrating. I wonder what type of problem would actually make restoring the website the only option. I guess if the plug-in messed with a database setting or some other custom code then it could cause this problem and require a full website restoration.


Leave a comment

Your email address will not be published.


Post Comment