login error Archives - Complete, Concrete, Concise

WordPress – Error 404 When Trying to Login – Take 2

richardsplanet — Tue, 21 Feb 2012 21:25:44 +0000

UPDATE 14-March-2013

It has been over one year since I have disabled W3 Total Cache and the problem has not reoccurred, thus leading me to suspect the problem was caused by W3 Total Cache since the problem only occurred when I was using W3 Total Cache.

UPDATE 23-May-2012

I now suspect the login problem is caused by W3 Total Cache.
It has been about 2 months since I disabled it because I kept getting site errors – including login errors. The errors have stopped.
My recommendations are: (1) try to login in using the techniques described here, (2) empty your W3 Total Cache caches, (3) disable W3 Total Cache.

I would appreciate feedback letting me know if:

you have W3 Total Cache installed and enabled when you get this problem, or
you get this problem but have some other caching plugin installed, or
you have no caching module installed and you still get this problem.

This is a real problem because I get a steady stream of hits on this page and, aside from this article, I don’t know of any real solutions to this problem. All other articles seem to be of the “do something (like touching file permissions) and the problem magically goes away” variety.

In December 2011, I had trouble logging into my site. I kept getting an Error 404: Not Found message. I documented what I did to resolve that here.

In February 2012, it happened again. After waiting 48 hours for the problem to resolve itself – and it didn’t – I began troubleshooting again. Fortunately, I had a few more facts this time around and a lot less panic or worry about having my site having been hacked.
What I knew: (1) my site was still accessible, (2) other people did not have problems leaving comments (during that time I received 1 legitimate comment, 3 SPAM comments, and 1 pingback) – even though I wasn’t able to leave a comment. (I tried a different computer, I tried a different browser, I tried a different OS, I tried a different IP address (depending on what type of Internet connection you have, turning your modem on and off may get you a new IP address) but none of them worked. The only thing I didn’t try for logging in from someone else’s Internet connection.)
I was able, though not consistently, to login by clicking on an action link in the e-mail WordPress sends me to tell me I have a new comment (since I have comment moderation turned on, WordPress e-mails me every time there is a new comment). Even if I was able to login, I was not able to do a lot in the Admin panel (replying to or deleting comments wouldn’t work).
I checked the WordPress error logs, there was nothing in them to suggest a problem.
I searched the web for solutions. Again, nothing useful came of it – lots of people have experienced this problem, but no useful solutions were offered (and those that were offered were more of the “do something – anything – and the problem will miraculously go away” type.
Checking my server logs, I could see 404 pages being delivered when I tried to log in. Nevertheless, the pages in question should exist (and I double checked that they did), so it didn’t make sense that they couldn’t be found.
Finally, while studying the WordPress login help page, and double checking everything on the page (even those I didn’t think made sense), I decided to try manually resetting my site’s URL as described in the section Site URL Redirecting. This worked! And it was reproducible – if I changed my URL I was able to login, if I set it back to the original URL I couldn’t login. This was good because a reproducible problem means the solution works – I think.
My original site URL was http://complete-concrete-concise.com – notice the lack of the www.prefix. While my site was and continues to be accessible without using www. before the name, when I changed it to http://www.complete-concrete-concise.com my login problem went away. And when I removed the www. the login problem came back.
What causes this? To be honest, I don’t know. My suspicion is it is a problem with the name server (the name server is a Internet server that looks up the site name and returns its Internet address).
For the first 8 months this site used WordPress (previously, I used Joomla!), this site used the name servers of my web host – without this problem occurring. Since switching to CloudFlare’s name servers (because I use them to relieve some of the bandwidth pressure on my web host) in December 2011, I have encountered this problem twice in 3 months. I don’t have enough evidence to conclusively claim this but others have had this problem with their web hosts
From what I can see, my DNS records with CloudFlare are fine, yet, changing my WordPress URL to use the www. prefix solves the issue – at least for now).

This solution assumes that:

the problem is an improperly resolved URL
your site can be accessed with or without the www. prefix
cPanel is your website administration panel provided by your webhost

Some images may be clicked for larger versions.

WARNING!!!! Messing around directly with your MySQL database can result in a completely NON-FUNCTIONING site.
Always make a backup before making any changes

1) Login to your web hosting control panel. This is not your WordPress admin panel. For many users this will be cPanel, but your webhost my provide you with a different website administration panel.
2) Click on the phpMyAdmin icon:

3) Click on your WordPress database in the left-hand side panel. If, like me, you run several websites from one account, you will have to find the appropriate database (in my case, it is not too hard, since I have one Joomla! site and one WordPress site and the database names are pretty obvious):

4) Click on wp_options in the left-hand side panel:

5) Locate the option name siteurl and click on Edit:

6) Change the URL name to your alternate one. My original URL was http://complete-concrete-concise.com. I changed it to include the www. prefix. If your original URL contains the www. prefix, and you have set up your name server to serve both versions, then remove the www. prefix. Click on Go to save the settings:

7) Check that you are able to login in to your website.

Caveat: While this worked for me (as did just waiting – see my original post on this problem), I make no guarantee. In looking for a solution to this problem, I see that lots of people have it, but I don’t see solutions to it.
Obviously, I would love to get feedback on this. I am still unclear on where the problem lies – is it a web hosting problem? is it a name server problem? is it a WordPress problem?

Update 28-Feb-2012: I restored my siteurl to its original value and my site continues to work correctly. I think this supports my original conclusion that patience is the solution – of course, waiting around for a few hours or even several days for it to resolve itself is not an option most would consider acceptable.
It also lends weight to the argument that it might be a DNS issue.

Update 02-Mar-2012: the error returned. sigh. Changing siteurl to use the www. prefix has, once again, fixed the problem.

The post WordPress – Error 404 When Trying to Login – Take 2 appeared first on Complete, Concrete, Concise.

WordPress – Error 404 When Trying to Login – Take 1

richardsplanet — Thu, 15 Dec 2011 13:48:11 +0000

This post was my original attempt at solving the Error 404: Not Found error when trying to login to my website.

It happened again and after waiting 48 hours for the problem to clear – it didn’t – I started searching for another solution.

My second solution (which was reproducible) can be found here

I think a reproducible problem / solution is better than a problem that mysteriously goes away after a while.

However, I am not 100% certain this problem is fully resolved. I will have to wait and see if it happens again.

If you are getting this message / error when you try to login and you used to be able to login just fine before, then the solution seems to be patience. This is likely a temporary problem with your webhost provider and is one of those problems that gets “miraculously” resolved several hours later.

It’s no fun to wait, but that seems to be the solution. Of course, you can always contact your webhost provider and let them know about the problem.

It took about 24 hours for this problem to go away for me (of course, some of those hours were spent sleeping, so it might have been less).

During this issue, the site was still active, but it was not possible to login in to the admin page or to leave comments.

I encountered this problem with WordPress 3.2.1, but searching the web, reveals this problem has occurred with other versions. From what I can tell, none of the stated solutions works – they just give you something to do (and I think it is the act of doing something – even if it seems pointless – that causes people to think the solution worked when just leaving it alone would have resolved the issue anyway).

Yesterday, I got a Error 404: Not Found error when trying to login to my site:

My first thought (well, after trying to login in a few times) was that my site had been hacked, then I focussed to resolve the problem.

How I Wasted My Day

The first thing I did was shut down my browser (IE 9), clear the cache and temporary files using CCleaner, and restart the computer. I thought it might be some sort of connection problem. That didn’t work.

Next I shut down my computer, turned off my modem and did some other things. I thought it might be a connection problem based on my IP address. My web host will automatically block IP addresses for an hour if it perceives a threat from that IP address. Turning off the modem means I will be assigned a new IP address when I turn it on a little later. That didn’t work.

I thought it might be my webhost acting up, so I logged into the CPanel backend, but everything seemed to be working fine.

To ease my concerns that I might have been hacked, I checked the date stamps on the WordPress files. They were all at least two weeks old (the last time I did an update) – no files had been changed in the past day – so I wasn’t worried about having been hacked.

I tried accessing my site through w.bloggar (a blogging client, similar to, but older, than Windows Live Writer – you can read why I use w.bloggar instead of WLW here), but that didn’t work, It told me that the response it received back was invalid.

Then I thought it might be CloudFlare acting up. This was harder to troubleshoot. I could always change the name servers back to the original name servers, thus bypassing CloudFlare’s name servers – but it would take up to 48 hours for the change to percolate through and, by that time, if it was a temporary issue, it might be resolved. I decided to (1) set CloudFlare to development mode – this means that for the next 3 hours, they pass all requests directly to my webhost. That didn’t work, then (2) I tried bypassing CloudFlare by accessing my site directly using my site’s IP address. That didn’t work either.

At this point, I decided to search the web for help – turns out, I am not the only one to ever experience this problem.

This site recommended changing the permission attributes on all the files and directories. Personally, I didn’t see the point. I checked my file permissions and they all seemed fine. I did not run the recommended fix because while some claimed it worked, others claimed it didn’t. I also had no desire to play with the core install (well, at least not yet).

WordPress has its own help page for login problems. None of the solutions worked. Some of them actually render your site unusable. For example, the codex states: Rename the active theme folder… Once renamed, WordPress will revert to using the WordPress TwentyEleven theme., doing that results in a site that just doesn’t work.

After a lot more research, some sites (a little past halfway down the page, comment by dremeda) suggest replacing the core WordPress files with ones from a clean install. Ugh! That sounds positively dangerous.

Instead, I created a new WordPress site with my webhost – this one allowed me to login. Then I zipped up the working and not working sites and downloaded them. Then I unzipped them and compared the files using emacs. There was no difference between the files. Hmm.

I then decided it would be safe to replace the core files of the “not working” WordPress site with the core files of the “working” WordPress site. This did not work either.

Being tired and out of ideas, I went to bed. This morning, everything worked fine.

The post WordPress – Error 404 When Trying to Login – Take 1 appeared first on Complete, Concrete, Concise.