Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Login loop after manually upgrading to NC 220.127.116.11 #11114
On a testing instance after upgrading from 13.0.6 to 18.104.22.168 I can not login anymore due to a redirect loop. This happens on two testing instances (SQLite3 and PostgreSQL)
Steps to reproduce
Only posting data from my SQLite3 installation below.
User should be logged in.
User gets redirected to login page
Nextcloud version: (see Nextcloud admin page)
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from:
List of activated apps:
Are you using external storage, if yes which one:
Are you using encryption:
Are you using an external user-backend, if yes which one:
Web server error log
Nextcloud log (data/nextcloud.log)
This is all from my nextcloud.log. New login-attempts are not logged in loglevel=2
The Browser log reflects the log from nginx:
GitMate.io thinks possibly related issues are #8829 (login loop), #10885 (NC 14.0.0 beta 4, web login failed after upgrade from 22.214.171.124), #10603 (Ideas for NC 14), #8199 (Redirect Loop after upgrading to 13.0 (InvalidSignatureException)), and #3134 (After upgrade from NC 10.0 to 11.0.1 --> slow performance).
I am the user in the forum. It should be noted that the issue only occurs with migration/upgrades, meaning it issue is likely to reside in the database changes during the upgrade itself or a missing file. Again, there is not useful log output to give a starting point.
In your output, there is a bit more useful information. The system is failing the integrity check on the redirect. I will dig into it over the evening with your information if no one else has solved yet. Marking for myself as a reminder.
Actually I am not sure whether that line with the integrity check has anything to do with the login loop as I noticed that nothing is written to the log when I try to login now. I have not idea where that line comes from as the integrity check done during the upgrade didn‘t report any errors (see last lines above the very last line in the log I posted in the initial post). Maybe I've been locked in during the upgrade and afterwards tried to refresh the page.
For further investigation I changed the nextcloud loglevel to 0 and these are the entries when I try to login (with correct credentials!) and the login loop occurs:
As you can see the in the very first line there is an exception thrown that I am not logged in - resulting in a 401 and a new request (redirect) to