Skip to content
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

Bitwarden admin console not accessible after update to 2024.7.4 #4678

Closed
1 task done
krauthex opened this issue Aug 19, 2024 · 1 comment
Closed
1 task done

Bitwarden admin console not accessible after update to 2024.7.4 #4678

krauthex opened this issue Aug 19, 2024 · 1 comment
Labels

Comments

@krauthex
Copy link

Steps To Reproduce

  1. self-host bitwarden 2024.7.2
  2. Update to 2024.7.4 via bitwarden.sh updateself and bitwarden.sh update
  3. Log in normally
  4. Try to access the admin console by clicking the Admin Console button

Expected Result

I expect to be able to access the admin console.

Actual Result

Nothing is happening. The logs of the bitwarden-web container after pressing the Admin console button show:

info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.0 GET http://bitwarden.REDACTED.at/212.c0081a53399535123db9.js - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.0 GET http://bitwarden.REDACTED.at/212.c0081a53399535123db9.js - 404 0 - 0.2166ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[16]
      Request reached the end of the middleware pipeline without being handled by application code. Request path: GET http://bitwarden.REDACTED.at/212.c0081a53399535123db9.js, Response status code: 404

Screenshots or Videos

No response

Additional Context

current versions of docker images in use after performing the update as described above:

bitwarden/notifications   2024.7.4   369f056e4c3b   11 days ago    334MB
bitwarden/mssql           2024.7.4   084a13f791d2   11 days ago    1.6GB
bitwarden/icons           2024.7.4   a7d5b1df7bc2   11 days ago    334MB
bitwarden/api             2024.7.4   afb194491df9   11 days ago    339MB
bitwarden/events          2024.7.4   e8249eb9b0e6   11 days ago    333MB
bitwarden/nginx           2024.7.4   cbce1bba5a2b   11 days ago    190MB
bitwarden/attachments     2024.7.4   2d99f48a4f4b   11 days ago    225MB
bitwarden/setup           2024.7.4   70d3bc3724ac   11 days ago    289MB
bitwarden/identity        2024.7.4   5dee220039b3   11 days ago    334MB
bitwarden/sso             2024.7.4   8e91f7b9cb8a   11 days ago    338MB
bitwarden/admin           2024.7.4   3918828a0df8   11 days ago    349MB
bitwarden/web             2024.7.3   8d9a59f0fc77   12 days ago    278MB
bitwarden/setup           2024.7.2   42d89789b758   3 weeks ago    289MB

Build Version

2024.7.4

Environment

Self-Hosted

Environment Details

  • Ubuntu 20.04.6 LTS
  • docker-ce 26.1.4
  • 2 CPU/4GB RAM VM instance in OpenNebula

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@krauthex krauthex added the bug label Aug 19, 2024
@krauthex
Copy link
Author

Ah dang, it seems like it was an error on my side. for some reason, my firefox caused the issue; opening bitwarden in a private window resolved the issue.... 🙈

nevermind then. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant