-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Cannot access admin menu #577
Comments
I can confirm this, encountered the exact same problem just now after updating. |
Thanks a lot for the very clear and detailed bug report @NullIsNot0 and apologies for the inconvenience! I know exactly what is causing this and will submit a fix now. |
Keep in mind that you'll need to apply the fix manually to your already existing |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On 9th of July I set up Sentry without changing anything in setup - just copying files to server and running
./install.sh
. Everything was working fine - I could access Admin menu http://mydomain.com:9000/manage/ and click through submenu items. Today I updated to latest version of this project, and I can't access admin menu (with first user created in system which has admin rights) - I get password prompt popup which does not go away if I enter password. If I enter incorrect password, it shows that password is incorrect, but when I enter correct password, it just pops up again.After reverting files back to commit 9d44b99 and running
./install.sh
anddocker-compose up -d
, admin menu started to work again.I found out that something is broken in 10th of July commit 73213bc.
I even installed clean system on test Linux. Latest project version did not allow admin menu access, but when I reverted it back to 9d44b99, menu was accessible again.
Tried both on CentOS 7 (with latest available packages) and Ubuntu 20.04. Docker version 19.03.12, Docker Compose 1.26.2.
Both times (when working and not working) Sentry build version was
Sentry 20.7.0.dev0 92b1577
- so it's not the problem in Sentry's Docker image as both times it wasgetsentry/sentry:92b1577
.Logs in Docker output when working:
Logs in Docker output when not working:
The text was updated successfully, but these errors were encountered: