Login fails on every umbraco app - didn't yesterday?!
Hi!
For some reason, I can't login to umbraco anymore - not on any of the installations we have on the same webserver. The front end still works just fine, and so did Umbraco until today.
The only thing I have done is installing a new website that uses a new Umbraco install. Can this be the cause??
Does anyone have ANY idea why this is happening?? Any help highly appreciated.
Hi Thomas! It seams like I can always rely on a quick reply from you. Thank you for that.
I'm not sure about the seperate appp pools. I installed most of the websites with the web platform installer. I can not check that from here. I have to return to you on that one tomorrow when I'm at work.
But I still think this would be strange, due to the fact that the front end works just fine. If the Application pool for some reason is down, would'nt the whole website be down? I did try to restart the website from IIS, which did not solved it either.
We actually had the same problem a couple of days ago, with a customer who couldn't logon, but I could (with the same logon at a different location). The customer returned an hour later, saying that now the problem had dissapeared. I just thought that was just our client who could use a computer ;-)
it is only a hazard that I am looking into the forum when you are posting ;-)
Sometimes there are some strange behaviours on IIS, ASP.NET and Caching. So the first thing to do in some strange behaviours is to reinitialize the app (touching web.config). If that fails you can recycle the application pool which reinitializes everything on the web application.
Per default there should be one application pool for each web application. One of the most important things about that is if the one app crashes the other app will continue running. If you only have one app pool for both apps both apps will stop working if one app crashes.
Just try to recycle the app pool and see what happens. ;-)
This just keeps stranger and stranger. I tried all the above, I even created a brand new AppPool for one of the sites, with no luck.
Then I remembered that we have had some problems setting the clock on the server - it keept resetting to 1. of april. Then our Server Administrator fixed that, but for some reason the date had been set to middle of december ( I guess X-mas comes yearly this year ;-) ) for the past two weeks. I corrected the date this monday. Just for the heck of it, I tried this morning to set the date to 1. january 2010 - and VOILA, the login works on all sites.
So I guess the question now is: How do I get Umbraco to work with the correct date??
Perhaps it is an issue with the cookies and the dates that the client cannot login correctly and will be logged out immediatly after the login because the server thinks the cookie is timed out? I would set the date of the server correct, do a complete server reboot, clear the client cookies and the cache and then try again.
Login fails on every umbraco app - didn't yesterday?!
Hi!
For some reason, I can't login to umbraco anymore - not on any of the installations we have on the same webserver. The front end still works just fine, and so did Umbraco until today.
The only thing I have done is installing a new website that uses a new Umbraco install. Can this be the cause??
Does anyone have ANY idea why this is happening?? Any help highly appreciated.
/Dan
Did you use seperate application pools for the umbraco installations?
Also I would try to recycle the application pools (restarting the app pools).
Thomas
Hi Thomas! It seams like I can always rely on a quick reply from you. Thank you for that.
I'm not sure about the seperate appp pools. I installed most of the websites with the web platform installer. I can not check that from here. I have to return to you on that one tomorrow when I'm at work.
But I still think this would be strange, due to the fact that the front end works just fine. If the Application pool for some reason is down, would'nt the whole website be down? I did try to restart the website from IIS, which did not solved it either.
We actually had the same problem a couple of days ago, with a customer who couldn't logon, but I could (with the same logon at a different location). The customer returned an hour later, saying that now the problem had dissapeared. I just thought that was just our client who could use a computer ;-)
Does any of this make any sense?
Hi Dan,
I had the same problem with a client last month. I recycled the Application Pool assigned to the clients site and that seemed to resolve it.
Tom
Hi Dan,
it is only a hazard that I am looking into the forum when you are posting ;-)
Sometimes there are some strange behaviours on IIS, ASP.NET and Caching. So the first thing to do in some strange behaviours is to reinitialize the app (touching web.config). If that fails you can recycle the application pool which reinitializes everything on the web application.
Per default there should be one application pool for each web application. One of the most important things about that is if the one app crashes the other app will continue running. If you only have one app pool for both apps both apps will stop working if one app crashes.
Just try to recycle the app pool and see what happens. ;-)
hth, Thomas
This just keeps stranger and stranger. I tried all the above, I even created a brand new AppPool for one of the sites, with no luck.
Then I remembered that we have had some problems setting the clock on the server - it keept resetting to 1. of april. Then our Server Administrator fixed that, but for some reason the date had been set to middle of december ( I guess X-mas comes yearly this year ;-) ) for the past two weeks. I corrected the date this monday. Just for the heck of it, I tried this morning to set the date to 1. january 2010 - and VOILA, the login works on all sites.
So I guess the question now is: How do I get Umbraco to work with the correct date??
/Dan
Perhaps it is an issue with the cookies and the dates that the client cannot login correctly and will be logged out immediatly after the login because the server thinks the cookie is timed out? I would set the date of the server correct, do a complete server reboot, clear the client cookies and the cache and then try again.
Just a guess.
Thomas
Once again Thomas, you are the man!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.