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

.NET errors appear after upgrading to 2024.12.1 and can no longer access web vault #5260

Open
1 task done
djpeck1 opened this issue Jan 14, 2025 · 1 comment
Open
1 task done
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment

Comments

@djpeck1
Copy link

djpeck1 commented Jan 14, 2025

Steps To Reproduce

  1. Go to bitwarden self-hosted URL
  2. Browser returns "502 Bad Gateway" nginx/1.27.3

Expected Result

Should be able to access the latest unified self-hosted beta web vault.

Actual Result

Browser returns "502 Bad Gateway" nginx/1.27.3

Looking at the logs for the Bitwarden container shows the following;

Adding group `bitwarden' (GID 20166) ...
Done.
Adding user `bitwarden' ...
Adding new user `bitwarden' (20162) with group `bitwarden (20166)' ...
Not creating home directory `/home/bitwarden'.
Adding new user `bitwarden' to supplemental / extra groups `users' ...
Adding user `bitwarden' to group `users' ...
You must install or update .NET to run this application.

App: /usr/local/bin/hbs
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
.NET location: /usr/share/dotnet

The following frameworks were found:
  8.0.1 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Learn more:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=linux-x64&os=debian.12

This problem was not present in the 2024.12.0 beta release.
I would appreciate assistance with this as I'm not sure how to proceed. (For now I have reverted to 2024.12.0 and everything is fine again)

Screenshots or Videos

No response

Additional Context

No response

Githash Version

https://{your-bitwarden-domain}/api/config and copy the gitHash version

Environment Details

Container-Optimized OS from Google version 101
Docker 20.10.27

Database Image

MariaDB version 11.6.2

Issue-Link

#2480

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.
@djpeck1 djpeck1 added bug bw-unified-deploy An Issue related to Bitwarden unified deployment labels Jan 14, 2025
@cbw23
Copy link

cbw23 commented Jan 15, 2025

Hi there,

This issue has been escalated for further investigation. If you have more information that can help us, please add it below.

You may also write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment
Projects
None yet
Development

No branches or pull requests

2 participants