Mike
Well-Known Member
Corley, there is one glaring flaw with your logic. If the problem with logging into your account were at the server end of the pipe, you would not be able to log in from any computer. Nor would I have been able to log into your account from here. If the forums were broken, they would be broken for everyone, no matter what computer they were using. If your account was broken, it would be broken for both of us, no matter what computer we were using.
As I've been hunting and searching for a solution to this problem, I've been finding isolated pockets of this same problem. And it seems to only affect a small percentage of the total users, same as here. And in most of those instances, people seem to be finding Google Chrome is more forgiving and will, in some instances, allow log-ins where other browsers will not. By simple observation, It seems 64 bit IE 8 users are the most affected, but I do not have hard data to support that. Although I've noticed a couple people running 64 bit IE 8 have tried running 32 bit IE 8 and solved the problem.
I know, several of you have pointed out this is the only site you are having problems with. But the fact the rest of us are not having any problems indicates the problem is not site-related. For those who were unable to log in and have passed along your details, I have been able to log into your accounts with no problems of any kind. This also indicates the problem is client-side.
Fact - The only thing that can cause a secure site to react as everyone is describing is a problem with cookies. We know the site is serving cookies properly, else I would not be logged in here. So we either have browsers that are not accepting cookies, or browsers with corrupted cookie files. The proof for that is the fact that some of you are logging in from one system when another system will not allow you to log-in. I know you all want this to be a problem at the server, but when one of your systems works and another one won't, we've localized the problem. When one of your browsers will work and another one won't, we've localized the problem.
Fact - I have always redirected all http://tbucketeers.com/ URLs to http://www.tbucketeers.com/ (note the dub-dub-dub), so that cannot be causing the problem. Try entering that first URL (without the dub-dub-dub) into your browser's address bar and then look at the address you end up on. Dub-dub-dub, every time. The new cookie format would eliminate this from being a problem anyway.
Fact - Since we converted to this forum software, I have never forced a cookie domain. Yesterday afternoon, I changed that so that the cookie domain will always be consistent. I also changed the cookie format, so that it would always have a -forum- prefix. That is a major change, yet the only users having a problem with it are those users who were already having problems. We've further localized the problem.
Fact - If the site were not serving cookies, none of us could ever log in. I don't know how to say this any more forcefully. The site is completely reliant on cookies being served to users' browsers and without that happening, the site will simply not allow anyone to log in. Ever. If I am posting here, that means I am logged into my account, which further means my browser has successfully accepted the session ID cookie from the site. Everything is working as intended, unless this post is a figment of my imagination.
Fact - If a member's account were somehow corrupted, they would never be able to log into that account. Corley can log in from some locations and not from others. Martin can log in with Chrome but not with IE 7. Lee cannot log in from his work system, but his home system works fine. I've logged into several problem accounts when the users could not. If the account were corrupt, it would be corrupt without exception. This further localizes the problem.
Now here's one that will really make you scratch your heads. I've now had two users e-mail me in the last 12 hours to say they have both heard from the IT Dept. at their respective places of employment that a recent Windows security update installed on their networks is causing multiple issues. In one instance, this update is causing programs required for work to be inaccessible. Why that is not affecting all Windows users, I have no idea. Why some browsers work when others will not, I have no idea.
I have now tested the site with Windows 7, Windows XP, Linux Mint Debian Edition, Linux Mint 10 Julia, Linux Mint 9 Isadora, Ubuntu 10.04 Maverick Meerkat and OS X Snow Leopard. I have tested the site with Firefox 3.5, Firefox 3.6, Firefox 4.0, Internet Explorer 8, Internet Explorer 9, Google Chrome 4, Google Chrome 10, Chromium 7, Opera 10, Safari 4, Safari 5, Epiphany 2 and Midori 0.3. I have tested the site with 4 different computers, a Dell Inspiron 15R, a Dell XPS 8100, a Dell XPS 410 and an Apple iMac. Four computers, seven operating systems, thirteen browsers and I cannot duplicate the problem with any of them. I log right in and I can access all member-only features and functions. I can even log into accounts inaccessible to their rightful owners, with no problems whatsoever. My Win 7 machine is 100% up to date with all the latest and greatest software and it works just fine. My XP installation is slow and cantankerous and had a lot of old software on it, but it works just fine. My iMac is fully updated and works just fine. I receive and install updates to the Linux installations, all day, every day. So I have brandy-new operating systems, and I have old operating systems. I have browsers being updated nightly and I have browsers that are growing beards. And every single combination of every single one of them all work 100%, without so much as a hiccup.
When someone like Lee cannot log into the site from one computer, that gives me cause for concern. When I can log into Lee's account from my own computers, I'm starting to suspect there is an issue with Lee's computer. When Lee can log into his account from a second computer, that only makes me look at the suspect computer that much harder. When Lee cannot log into his account from only one computer and 100+ other members are logging in and out without problems, I have to point the finger at that one computer. It is a simple process of elimination. When everything works from Computer A and everything works from Computer B, then that means there is something different about Computer C. How can we possibly localize a problem any further than that?
I don't like this any more than the people who cannot log in. I spent over 10 hours working with this problem, yesterday. I earned zero income yesterday, because I spent the day trying to chase this down. I've talked with other admins and with code monkeys, all who have suggested I advise everyone with the problem to clear their cache history or to try an alternative browser. What novel ideas, eh? I've scanned countless Web pages, looking for a more solid method of establishing the cookie domain and cannot find anything other than what we're already using. I've scanned cookie files from several different browsers, looking for inconsistencies and there are none. I've read Windows security update pages. I've read browser help forums. I've read help files on just about any forum software package I can think of. In every, single instance where a similar problem is identified, the recommended solution is to clear cache history, ensuring all cookies are cleared. Go figure. A tiny handful of users cannot seem to log in, no matter what we have tried. Some other users cannot seem to log in from certain systems. Yet the lion's share of users are logging in and logging out without any problems.
I'm going to continue trying to find a solution to the problem, but I am now completely confident the forum software, the MySQL database and Apache are all doing their jobs as intended. Now it is a matter of trying to discover why only some of you are having problems when the rest of us are not.
As I've been hunting and searching for a solution to this problem, I've been finding isolated pockets of this same problem. And it seems to only affect a small percentage of the total users, same as here. And in most of those instances, people seem to be finding Google Chrome is more forgiving and will, in some instances, allow log-ins where other browsers will not. By simple observation, It seems 64 bit IE 8 users are the most affected, but I do not have hard data to support that. Although I've noticed a couple people running 64 bit IE 8 have tried running 32 bit IE 8 and solved the problem.
I know, several of you have pointed out this is the only site you are having problems with. But the fact the rest of us are not having any problems indicates the problem is not site-related. For those who were unable to log in and have passed along your details, I have been able to log into your accounts with no problems of any kind. This also indicates the problem is client-side.
Fact - The only thing that can cause a secure site to react as everyone is describing is a problem with cookies. We know the site is serving cookies properly, else I would not be logged in here. So we either have browsers that are not accepting cookies, or browsers with corrupted cookie files. The proof for that is the fact that some of you are logging in from one system when another system will not allow you to log-in. I know you all want this to be a problem at the server, but when one of your systems works and another one won't, we've localized the problem. When one of your browsers will work and another one won't, we've localized the problem.
Fact - I have always redirected all http://tbucketeers.com/ URLs to http://www.tbucketeers.com/ (note the dub-dub-dub), so that cannot be causing the problem. Try entering that first URL (without the dub-dub-dub) into your browser's address bar and then look at the address you end up on. Dub-dub-dub, every time. The new cookie format would eliminate this from being a problem anyway.
Fact - Since we converted to this forum software, I have never forced a cookie domain. Yesterday afternoon, I changed that so that the cookie domain will always be consistent. I also changed the cookie format, so that it would always have a -forum- prefix. That is a major change, yet the only users having a problem with it are those users who were already having problems. We've further localized the problem.
Fact - If the site were not serving cookies, none of us could ever log in. I don't know how to say this any more forcefully. The site is completely reliant on cookies being served to users' browsers and without that happening, the site will simply not allow anyone to log in. Ever. If I am posting here, that means I am logged into my account, which further means my browser has successfully accepted the session ID cookie from the site. Everything is working as intended, unless this post is a figment of my imagination.
Fact - If a member's account were somehow corrupted, they would never be able to log into that account. Corley can log in from some locations and not from others. Martin can log in with Chrome but not with IE 7. Lee cannot log in from his work system, but his home system works fine. I've logged into several problem accounts when the users could not. If the account were corrupt, it would be corrupt without exception. This further localizes the problem.
Now here's one that will really make you scratch your heads. I've now had two users e-mail me in the last 12 hours to say they have both heard from the IT Dept. at their respective places of employment that a recent Windows security update installed on their networks is causing multiple issues. In one instance, this update is causing programs required for work to be inaccessible. Why that is not affecting all Windows users, I have no idea. Why some browsers work when others will not, I have no idea.
I have now tested the site with Windows 7, Windows XP, Linux Mint Debian Edition, Linux Mint 10 Julia, Linux Mint 9 Isadora, Ubuntu 10.04 Maverick Meerkat and OS X Snow Leopard. I have tested the site with Firefox 3.5, Firefox 3.6, Firefox 4.0, Internet Explorer 8, Internet Explorer 9, Google Chrome 4, Google Chrome 10, Chromium 7, Opera 10, Safari 4, Safari 5, Epiphany 2 and Midori 0.3. I have tested the site with 4 different computers, a Dell Inspiron 15R, a Dell XPS 8100, a Dell XPS 410 and an Apple iMac. Four computers, seven operating systems, thirteen browsers and I cannot duplicate the problem with any of them. I log right in and I can access all member-only features and functions. I can even log into accounts inaccessible to their rightful owners, with no problems whatsoever. My Win 7 machine is 100% up to date with all the latest and greatest software and it works just fine. My XP installation is slow and cantankerous and had a lot of old software on it, but it works just fine. My iMac is fully updated and works just fine. I receive and install updates to the Linux installations, all day, every day. So I have brandy-new operating systems, and I have old operating systems. I have browsers being updated nightly and I have browsers that are growing beards. And every single combination of every single one of them all work 100%, without so much as a hiccup.
When someone like Lee cannot log into the site from one computer, that gives me cause for concern. When I can log into Lee's account from my own computers, I'm starting to suspect there is an issue with Lee's computer. When Lee can log into his account from a second computer, that only makes me look at the suspect computer that much harder. When Lee cannot log into his account from only one computer and 100+ other members are logging in and out without problems, I have to point the finger at that one computer. It is a simple process of elimination. When everything works from Computer A and everything works from Computer B, then that means there is something different about Computer C. How can we possibly localize a problem any further than that?
I don't like this any more than the people who cannot log in. I spent over 10 hours working with this problem, yesterday. I earned zero income yesterday, because I spent the day trying to chase this down. I've talked with other admins and with code monkeys, all who have suggested I advise everyone with the problem to clear their cache history or to try an alternative browser. What novel ideas, eh? I've scanned countless Web pages, looking for a more solid method of establishing the cookie domain and cannot find anything other than what we're already using. I've scanned cookie files from several different browsers, looking for inconsistencies and there are none. I've read Windows security update pages. I've read browser help forums. I've read help files on just about any forum software package I can think of. In every, single instance where a similar problem is identified, the recommended solution is to clear cache history, ensuring all cookies are cleared. Go figure. A tiny handful of users cannot seem to log in, no matter what we have tried. Some other users cannot seem to log in from certain systems. Yet the lion's share of users are logging in and logging out without any problems.
I'm going to continue trying to find a solution to the problem, but I am now completely confident the forum software, the MySQL database and Apache are all doing their jobs as intended. Now it is a matter of trying to discover why only some of you are having problems when the rest of us are not.