I think I had this problem once, the solution was to do a progressive update, to every major version in between. In your case, it would be an upgrade to 7.0 and then to 7.7.9
Not for this project but i did another upgrade had similar issue and fixed that my updating the web.config membership part also i did upgrade by creating blank umbraco site i wanted to upgrade to then pointed it to my existing db then did a deploy.
had a similar issue a while ago not sure if exactly the same but, the old site used usernames to log in and after upgrade the default logic is to use email address.
I remember having to edit the providers if the web config to allow the legacy way of logging in i.e.
I have the same issue after upgrading from 7.2.2 to 7.8.1. I tried how far I could go and up until 7.6.13, there are no problems. With 7.7.0, the login suddenly stops working. I always get the 'Authentication/PostLogin Internal Server Error (500)'.
Things I've tried so far:
useLegacyEncoding true/false (true should be working in my case)
Copying web.config from a working project
Adding customHeaders for 'Access-Control-Allow-Origin' and 'Access-Control-Request-Headers' with value '*' in the web.config
Copying DB table layout (umbracoUser) from a working project (incl. rows)
Manually downloading/replacing umbraco files
Upgrading umbraco via nuget update
Checked userNoConsole=0
Deleting App_Data; resetting cache; incognito mode; deleting bin
I've spent 3 hours searching for solutions but none seem to work for me. The login post request doesn't go through, because I can enter a wrong password as often as I want without the DB or log registering failed login attempts.
Just out curiosity is your site on azure as a web app or on an actual server, cloud or otherwise. The reason why i ask is i noticed in my case was an azure app and i was deploying direct from visual studio and did notice some of the files were not being updated with the new 1s, especially the ones in the umbraco folders, so had to physically delete theme from the app then deploy again.
The site is hosted on an actual server. I've updated already several other sites to version 7.8.1 without any issues, but the previous version of these was always 7.5.x+.
My next step will be to do a clean install of version 7.2.2 and update it to 7.8.1. I'll let you know whether the login works after that or not. If it does, then it's a configuration issue on my end.
In essence, Umbraco changed how users work for Umbraco 7.7, so you need to upgrade to that version first, and then you can upgrade to the latest version.
Upgrade now cannnot log in
Guys,
I have just upgraded a site from 7.6.1 to 7.7.9 and when i hit site it wants me to login to run the upgrade however the credentials no longer work.
I am not locked out checked the umbracoUsers table and i have useLegacyEncoding="true" still cannot login.
Also looking at console output i get error 400 bad request
Anyone seen this before.
Regards
Ismail
do you have DB backup before the upgrade? could you check if password hash didn't change?
Pawel,
Will check that in the db as its sql ce and checked into source control.
Regards
Ismail
Pawel,
No password hash has not changed.
Regards
Ismail
Ismail,
I think I had this problem once, the solution was to do a progressive update, to every major version in between. In your case, it would be an upgrade to 7.0 and then to 7.7.9
Hi,
Could it just be a corrupt session - have you tried hitting the site from a browser you don't use or in incognito mode?
I've seen some cookie / session issues mean I can't log in after upgrades.
Guessing you've already tried this though?
Steve
Ismail, did you ever figure this out?
Not for this project but i did another upgrade had similar issue and fixed that my updating the web.config membership part also i did upgrade by creating blank umbraco site i wanted to upgrade to then pointed it to my existing db then did a deploy.
Regards
Ismail
had a similar issue a while ago not sure if exactly the same but, the old site used usernames to log in and after upgrade the default logic is to use email address.
I remember having to edit the providers if the web config to allow the legacy way of logging in i.e.
Try that think the key setting is the use legacy encoding
I have the same issue after upgrading from 7.2.2 to 7.8.1. I tried how far I could go and up until 7.6.13, there are no problems. With 7.7.0, the login suddenly stops working. I always get the 'Authentication/PostLogin Internal Server Error (500)'.
Things I've tried so far:
I've spent 3 hours searching for solutions but none seem to work for me. The login post request doesn't go through, because I can enter a wrong password as often as I want without the DB or log registering failed login attempts.
Any other ideas I could try?
Jeremy
Just out curiosity is your site on azure as a web app or on an actual server, cloud or otherwise. The reason why i ask is i noticed in my case was an azure app and i was deploying direct from visual studio and did notice some of the files were not being updated with the new 1s, especially the ones in the umbraco folders, so had to physically delete theme from the app then deploy again.
The site is hosted on an actual server. I've updated already several other sites to version 7.8.1 without any issues, but the previous version of these was always 7.5.x+.
My next step will be to do a clean install of version 7.2.2 and update it to 7.8.1. I'll let you know whether the login works after that or not. If it does, then it's a configuration issue on my end.
Jeremy
For anybody who is curious, my issue was a bug with the Umbraco core: http://issues.umbraco.org/issue/U4-11300
In essence, Umbraco changed how users work for Umbraco 7.7, so you need to upgrade to that version first, and then you can upgrade to the latest version.
That's probably the cleanest workaround. Somebody else posted another workaround though: http://issues.umbraco.org/issue/U4-11258#comment=67-46492
Since my issue was actually a duplicate, I encourage anybody who runs into this to vote on the original issue: http://issues.umbraco.org/issue/U4-11258
Just wanted to share that the the solution for me was to first go to 7.7.13 and then to latest version (at the moment 7.11.1)
is working on a reply...