Session timeout after a few seconds in Umbraco

I created the site on Umbraco 7.1.6, it worked fine on Visual Studio 2012; when i deployed it to my hosting space i found the problem that it redirects me to the login screen over and over after a few seconds. I set the user account to true and increased the timeout but did not improve.

When I was looking for this problem I found several links:

The first link will give me the file, but I don't know how to update the current site.

I get an error in the console.

GET http://example.com/umbraco/backoffice/UmbracoApi/Authentication/GetRemainingTimeoutSeconds 401 (unauthorized) angular.min.js: 106 (anonymous function) angular.min.js: 106o angular.min.js: 102g angular.min .js: 100i angular.min.js: 79i angular.min.js: 79 (anonymous function) angular.min.js: 80e. $ Eval angular.min.js: 92e. $ Digest angular.min.js: 90e. $ Apply angular.min.js: 92safeApply umbraco.services.js: 58 (anonymous function) umbraco. services.js: 6773 (anonymous function) angular.min.js: 108e angular.min.js: 31 (anonymous function)

+3


source to share


2 answers


Thanks to everyone, especially @Morten Oc who commented.

This is correct something on the hosting. Have you tried other Umbraco installations on hosterpk? Also try setting your login time (in webconfig) to 0.

I found out it had to do with the hosting environment (permissions), I deployed to client hosting and works great.



Also, if you do not have full trust then it will not be able to maintain its session, you will have to configure the session to be managed in the database.

See this post for details on setting:

https://www.saotn.org/configure-sqlserver-sessionstate-for-umbraco/

+1


source


I just experienced the same symptoms. The site worked very well locally using IIS Express, worked great when deployed to Azure WebSites, but when I was working in a Windows Shared Hosting environment, the back office session would have stayed somewhere between a couple of seconds and two minutes.

I would get an authentication popup often, but not always at the GetRemainingTimeoutSeconds url.



I submitted a ticket and the provider was able to reproduce the problem. They said the site was operating in full confidence.

After enabling support for 32-bit applications - the problem is fixed.

+2


source







All Articles