Problem staying logged in all the time (using firefox)

[thenomad]

I am using Firefox 2.0.0.4 both on windows XP professional and Ubuntu Linux and I can not stay logged in for longer than, say may be an hour of inactivity or even less, I did not time it exactly. And this seems like an odditiy to me. I like to be able to check the stats of my web pages every couple of hours or so but every time I refresh the main projects page, I get "not logged in" screen and forced to re-login. With firefox this is not difficult as I keep my password stored in the password database, but again, logging in takes forever (or at least feels like it in today's impatience standards) and I'd like to avoid it.

I am tried the "remember me" box checked and unchecked to no noticeable difference in my opinion.

Does anyone suffer from this problem ? If yes, were you able to find a remedy ?

Thanks for your answers

[Car Guy]

Be sure your browser is accepting cookies.

You can specify "statcounter.com" as "allowed", and "my7.statcounter.com" etc.

Be sure to leave the "Remember me" checked.

Richard

[rhondafae]

Browsers limit the number of cookies you can set for any one site and since StatCounter users are abundant, you might have exceeded the limit!

Try this great little link:

http://my.statcounter.com/remove_cookies.php

This will remove all StatCounter cookies.

Try setting the "Remember me" cookie after visiting that link. Now don't log out of Statcounter - - that will destroy the "remember me" cookie!

[evilpanda]

I have the same problems with staying logged in so have just tried the above suggestion and will report back later

[thenomad]

I tried the suggestion and it failed. If I stay inactive, say about an hour or so (one can check the log so-frequently, not any more frequent) and I find myself facing a "login failed" message. And since firefox keeps the username password pairs on URL basis and StatCounter directs the user to one of the many servers, I am finding myself going to the main page and using my stored password on this page.

There is something wrong with either the cookie placement or with the cookie expiration. Don't know which one.

[BGL]

This has recently started happening to me also, using FF, last ~day or so. 2 Diff machines (work & home) - wasn't doing this before, or at least; near as often. FF 1.5 @ home & work.

[thenomad]

Update:
Today, I tested the "clear cookies" suggestion above and when I tried to refresh my projects page 32 minutes (according to my computer's clock) I was directed to the login failed screen.
I will continue to check the situation with shorter time intervals but seems like 30 minutes is the magic number.
Can someone from StatCounter team verify this and show us how to circumvent that ? I am not looking into staying logged in months at a time but a reasonable inactivity period should not be less than 24 hours in my opinion.

[BigMumu]

I'm getting same problem on Opera too & cookies are enabled, dunno why for some sites I'm logged in for weeks & for others there's that annoying limit ..

[yarnjunkie]

Same problem here but it hasn't been an issue before. I'm not really sure what's going on. Also, after I exit the "Create Blocking Cookie" page it resets itself without saving the changes I've made which is getting pretty annoying. Something is amiss, that's for sure! Hopefully the powers that be are reading this


edited to add that I tried this advice and it worked for me...so far anyway. Thanks!

Originally Posted by rhondafae

Browsers limit the number of cookies you can set for any one site and since StatCounter users are abundant, you might have exceeded the limit!

Try this great little link:

http://my.statcounter.com/remove_cookies.php

This will remove all StatCounter cookies.

Try setting the "Remember me" cookie after visiting that link. Now don't log out of Statcounter - - that will destroy the "remember me" cookie!

[rhondafae]

There's not a problem with the cookie we're offering. What you need to realize is that, StatCounter can offer the login cookie, but what happens beyond that depends on your computer.

It's very possible that without your knowledge, your security settings have been changed. You must make SURE that the StatCounter cookie is being set, and retained after the browser is closed. This is fairly simple to do, and I'll even provide you a "Cookie array" url to help:

http://my2.statcounter.com/view_cookies.php


Once you've set the login cookie, you should see it displayed.

"X" out of Statcounter - - Don't log out!! This will destroy the cookie!

You may have too many cookies. Browsers limit the number you may have from any one site, so you may want to flush your cookies before setting the login cookie, or you can clear JUST your StatCounter cookies by using this link:

http://my.statcounter.com/remove_cookies.php

Now, this will remove ALL Statcounter cookies, so you may need to reset the blocking cookie.

People who upgraded Firefox to version 2.0 - - listen up! It turns out that FF 2.x no longer has an "easy" setting procedure for (dis)allowing third party cookies, whereas apparently FF 1.x did.

To get to the settings:

1. Open a new tab in FF
2. In the URL window, type "about:config"
3. Go down the list in the window to "network.cookie.cookieBehavior"
4. If you're having a problem with StatCounter's cookies, the number value shown in this line is probably 1.
5. To stop blocking third party cookies, such as StatCounter, change the setting to "0".
6. Close it up.

That should fix the problem.

You can learn much more at http://forums.mozallazine.org and search for "third party cookies." Then read through the posts.

Additionally, FF offers you an option to delete cookies when the browser is closed. You need to change that by clicking:

Tools/options/privacy.

You'll see it there.

Finally, what programs are you running to "clean" your machine? Cleaning usually means deleting cookies - - you have to configure the settings to retain the StatCounter cookies if possible, and if not, you'll have to reset them.

If you've made it this far, you should have the tools to determine why you're cookie isn't being set or kept. This is only addressing the cookie issue, not the length of time you can remain inactive before you're logged out. That is a issue for our developers, and I'll be happy to check on that, Monday. I DO know that you're logged out for security reasons, but I can't recall how long that takes.

I hope this helps, guys. The only other thing I can think of is to check the clock on your system - - if the year is way off, it could expire the cookie. Far-fetched, but I've seen it!

Thanks!