Bug #19883
timout after backend login in 4.2.4
| Status: | Resolved | Start date: | 2009-01-21 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Christian Kuhn | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.2 | Is Regression: | ||
| PHP Version: | 5.2 | Sprint Focus: | ||
| Complexity: |
Description
Each time when I have logged into the backend, I am logged out immediately and get:
--------------------------------------------
Login-error or session timed-out
No user logged in! Sorry, I can't proceed then!
(You must have cookies enabled!)
If your session has just timed-out, you may
click here to re-login.
-----------
So I cannot login any more into the backend.
This happens in FF3 and Epiphany 2.24.0.1 .
It works fine in IE6.
It does not help to clear all caches.
(issue imported from #M10221)
Related issues
History
#1 Updated by Franz Holzinger over 6 years ago
The cookies for the backend must be cleared. Then it works.
#2 Updated by Christopher Hlubek about 6 years ago
Sorry, clearing just the cookies is not enough. This problem (or a similar problem) occurs even on new installations that are visited the first time! This is a very major problem for our clients and us.
The issue can be reproduced in the latest TYPO3 version (4.2.8). It works on the second login attempt though.
#3 Updated by Christian Kuhn about 6 years ago
Do you run several typo3 installations under one domain with subpathes?
eg.
foo.com/install1/typo3/
foo.com/install2/typo3/
Something like that?
#4 Updated by Michael Raberger about 6 years ago
Maybe this issue is related to this one: http://bugs.typo3.org/view.php?id=11538
#5 Updated by Christian Kuhn about 6 years ago
Other solutions:
- Server / Client Timezone work
- cookieDomain in localconf.php wrong
#6 Updated by Christopher Hlubek about 6 years ago
- Server / Client Timezone and time is perfectly in sync between Client and Server
- cookieDomain is not set
The problem is mostly solved by clicking on "re-login" and logging in again. Most of the time it is only the first login that fails.
#7 Updated by Andreas Wolf about 6 years ago
I also experience this problem from time to time. The only thing I noticed was that I was logged in on two installations under the same domain at the same time - that's what Christian also pointed out.
#8 Updated by Christian Kuhn about 6 years ago
Andreas, this should be solved with T3 4.1.11, 4.2.8 and trunk and was done with #19916 .
But the error will still occur, if you are logged in to one instance with a lower version (eg. 4.2.1) and then try to log in to another instance with 4.2.8. Solution: Update all your installations of this domain ...
#9 Updated by Lina Wolf almost 6 years ago
I dont think that this bug weas resolved with the other bugfix. The logout in IE8 also happens when there is just one TYPO3 Installation under the domain.
#10 Updated by Jo Hasenau over 5 years ago
Check #21511
#11 Updated by Christian Kuhn over 5 years ago
Resolved, no change required:
We had several thing that are all covered by related issues:
- The cookie problem solved the issue for the original author
- The subdomain thing is handled in some other isue
- The IE8 problem is already solved in core with this weird compatibility tag and covered by other issues
Let's close this issue for now and see if we still get new issues for current versions with more detailed bug analysis.