-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Visiting admin page shows 502 Bad Gateway nginx #3635
Comments
Working older version (11 days ago): |
Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again! |
As I've just upgraded my Bitwarden install from 2023.12.0 to 2024.1.0, I too ran into this issue. However, I've done some digging around and added some findings to this issue: #3651 (comment) To summarize, what I could see was that I do like to point out though that I am running MySQL 8.0.35 and the platform is ARM64, so this issue does not appear to be specific to MariaDB nor AMD64. I did find a way to somewhat work around the issue which involved some manual queries but I managed to get the Bitwarden instance running again (Warning for anyone attempting this manual "fix": these commands are destructive and can cause data loss if you're not careful. Make sure you know what you are doing!)
|
@mitchellvanbijleveld can you pull the latest from |
@withinfocus I am sorry to have you ask, but pulling from The
|
@withinfocus the admin logs show the following:
|
And here is another example of
|
You don't seem to have the latest is all -- I was referring to code merges in this repo, specifically commit |
Having the same issue with self-host:beta and self-host:2024.1.0-beta, so tried pulling the self-host:dev that have been updated 11 hours ago and the issue is still there. for now i reverted back to running self-host:2023.12.0-beta admin.log:
|
Yes, this is the same one I'm using too until testing each new version with positive results... |
Great! Let me check this afternoon :). |
self-host:beta 2024.1.2 dca8d00-dirty still gives me the same error |
You wouldn't get the same error as the MySQL migration changed. It now runs what you can see at https://github.com/bitwarden/server/blob/main/util/MySqlMigrations/Migrations/20231214162533_GrantIdWithIndexes.cs#L75-L90 that will delete and re-add the new |
Steps To Reproduce
Upgrading the Bitwarden installation from the December beta release to the beta release of the 2nd of January, 2024.
Expected Result
The browser shows Bitwarden's admin page to put in an email address to get a login link.
Actual Result
The browser shows: 502 Bad Gateway nginx
Screenshots or Videos
No response
Additional Context
nginx shows errors, something like
Also, data/bitwarden/logs/admin.log shows:
Githash Version
919d759-dirty
Environment Details
Running Debian 12, AMD64. This is nginx's config file:
Database Image
docker-compose.yml:
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: