New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Listed projects are "not authorized": Opening any project redirects to login page, after upgrade #177
Comments
At this point, I'm just trying to get it running as it used to. This is what I have tried:
And the same problem from above persists ("not authorized"). How is that possible? I have the same toolkit version and Overleaf version, so restoring the data folder should have worked, shouldn't it? These are a few differences that I found during this procedure:
I have also tried to dig into the source code to see where the authentication fails. According to the stack trace from above (real-time logs), this fails at /var/www/sharelatex/real-time/app/js/WebApiManager.js, which in turn connects to the URL |
Problem found: A proxy was configured in the environment variables of the container, and Overleaf was using that to communicate with the docstore host. I removed the proxy from It is unclear to me whether the internal docker network communication is ever supposed to go through a configured proxy or not, so I am leaving this open. |
I tried to upgrade Overleaf via the toolkit from 3.0.1 to the current version 4.0.4. That did not work because of a compatibility error message in MongoDB (which has since been lost), so I have tried to downgrade back to 3.0.1 and then up to 3.1.0. Then there was no compatibility error message any more, but when I log in and click on a project, the loading animation appears, and then I am redirected to the login page with a redirection query (e.g.
/login?redir=%2Fproject%2Fabcdef1234567890abcdef12
). However, opening the Overleaf home URL, I am still logged in.I have already tried to roll back to the last working version by (1) changing
config/version
back to3.0.1
and (2) restoring thedata
folder, but to no avail. What else could I try and which logs should I look into? I would like to avoid any data loss.Steps to Reproduce
data
directorybin/upgrade
bin/up -d
, container will repeatedly throw an error and restartconfig/version
bin/up -d
.Expected Behaviour
The project should have been opened after trying to open it.
Observed Behaviour
The loading animation starts and eventually I am being redirected to the login page (e.g.
/login?redir=%2Fproject%2Fabcdef1234567890abcdef12
), although I am logged in.Context
Technical Info
Analysis
The only meaningful message I could find on client side was "not authorized" from socket.io. On the server side, only the component "real-time" had a few insights. The following is the log from "real-time" after I clicked on a project that is mine and was listed on the project page:
The text was updated successfully, but these errors were encountered: