4

I have created an site on Umbraco 7.1.6 it was working perfect in Visual studio 2012; when I deployed it to my hosting space I found a problem that it redirects me to login screen again and again just after some seconds. I have set keep user login to true and increased timeout but no improvement.

When I searched for that problem I found some links:

First link provide me file but I do not know how to updated my current site.

In console I am getting an error.

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)

halfer
  • 19,824
  • 17
  • 99
  • 186
syed Ahsan Jaffri
  • 1,160
  • 2
  • 14
  • 34
  • 1
    Any errors in the console? And does the Network Service (or what IIS role you have) have write access to the whole umbraco website? – Morten OC Aug 30 '14 at 15:36
  • @MortenOC Yes, GetRemainingTimeoutSeconds throw 401 error. 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) – syed Ahsan Jaffri Aug 31 '14 at 04:58
  • 2
    I believe Umbraco 7 require a full trust hosting, and it needs to support forms authentication. What hosting provider are you using? @syedAhsanJaffri – Morten OC Aug 31 '14 at 07:13
  • @MortenOC http://www.hosterpk.com/ i have enabled form authentication too. On my local deployment IIS working fine when i change time on machine it behaves similar – sharafjaffri Aug 31 '14 at 08:21
  • 1
    Its properly something on the hosting. Have you tried other umbraco installations on hosterpk? Also, try to set the login time (in webconfig) to 0. – Morten OC Aug 31 '14 at 14:16
  • @MortenOC i have tried other cms but not umbraco – syed Ahsan Jaffri Aug 31 '14 at 14:49
  • 2
    @MortenOC Thanks alot for your efforts and suggestions. problem was due to hosting environment (Permissions), I deployed on client's hosting it works perfect – syed Ahsan Jaffri Aug 31 '14 at 18:14
  • 1
    post this as an answer and close this question... someone with this problem may skip to read as question is unanswered. – Chaitanya Gadkari May 21 '15 at 15:16

2 Answers2

2

Thanks to everyone, especially to @Morten Oc who commented.

It's properly something on the hosting. Have you tried other Umbraco installations on hosterpk? Also, try to set the login time (in webconfig) to 0.

I found out a solution that it was due to hosting environment (permissions), I deployed on client's hosting and it works perfectly.

Additionally if you do not have full trust hosting then it would not be able to maintain its session, you would have to configure session to managed in database.

For more info how to configure please refer to this post:

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

halfer
  • 19,824
  • 17
  • 99
  • 186
syed Ahsan Jaffri
  • 1,160
  • 2
  • 14
  • 34
2

I just experienced the exact same symptoms. A site ran just fine locally, using IIS Express, worked fine when deployed to Azure WebSites, but when I ran on a Windows Shared Hosting environment, the back office session would timeout somewhere between a couple seconds and a couple minutes.

I'd get a pop-up authentication window often but not always on the GetRemainingTimeoutSeconds url.

I filed a ticket, and the provider was able to replicate the issue. They said the site was running in full trust.

After enabling 32 bit application support - the issue is resolved.

Zeph
  • 1,728
  • 15
  • 29