Unified deployment no longer runs because of missing .NET about server HOT 44 CLOSED

Agree. This should be considered a showstopper severity issue. Surprised it's not fixed yet.

from server.

I too got the same errors and also rolled back "2024.1.2-beta". Using sqlite db.

Edit: Appears .Net was updated bitwarden/self-host#208

from server.

Just tried the latest push (3 hours ago). Still getting this error:
bitwarden_1 | /entrypoint.sh: line 85: 41 Aborted (core dumped) /usr/local/bin/hbs

from server.

Same problem here as well, only started with the latest version.

Rolling back to the bitwarden/self-host:2024.1.2-beta image works great. Just as everyone above, I have the same dotnet error (container fails to start).

Update:
Running dotnet --version initially on my server showed: 6.0.126
I'm running a RHEL-based distro, and upgraded: sudo dnf install dotnet-sdk-8.0
Rebooted the server.
Running dotnet --version now shows 8.0.101

... and unfortunately, the error still persists. BW container doesn't start with the same error.

from server.

Why does it take so long to fix this? Just add .net 6 to the image, even if it is temporary. Can this get some more prio please

from server.

Latest release (pushed a day ago) has the following error:
bitwarden_1 | /entrypoint.sh: line 85: 41 Aborted (core dumped) /usr/local/bin/hbs

from server.

Agreed, this has been a system breaking issue for several weeks now and should be higher priority as anyone using unified beta cannot upgrade for security, functionality, or bug fixing purposes. Is it possible for this to be resolved this week?

from server.

As others have mentioned, this specific issue was resolved, but now the issue is #3820

from server.

Confirmed. A rollback solved the issue for me as well.

from server.

Same problem here, rolled back to 2024.1.2

from server.

I received this log message via Docker Compose after updating Bitwarden (Unified) this morning:

bitwarden  | Adding group `bitwarden' (GID 1000) ...
bitwarden  | Done.
bitwarden  | Adding user `bitwarden' ...
bitwarden  | Adding new user `bitwarden' (1000) with group `bitwarden (1000)' ...
bitwarden  | Not creating home directory `/home/bitwarden'.
bitwarden  | Adding new user `bitwarden' to supplemental / extra groups `users' ...
bitwarden  | Adding user `bitwarden' to group `users' ...
bitwarden  | You must install or update .NET to run this application.
bitwarden  | 
bitwarden  | App: /usr/local/bin/hbs
bitwarden  | Architecture: x64
bitwarden  | Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
bitwarden  | .NET location: /usr/share/dotnet
bitwarden  | 
bitwarden  | The following frameworks were found:
bitwarden  |   8.0.1 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
bitwarden  | 
bitwarden  | Learn more:
bitwarden  | https://aka.ms/dotnet/app-launch-failed
bitwarden  | 
bitwarden  | To install missing framework, download:
bitwarden  | https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=linux-x64&os=debian.12

We worked around the issue by moving from the "beta" tag to the "2024.1.2-beta" tag.

from server.

@kociubin

Hi there,

Thank you for your report!

This issue has been flagged this to our engineering team for further investigation.

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!

from server.

Same here. Rolled back and all is okay for now. After my MariaDB crashed and burned a few weeks back and I re-setup everything with SQLite I was a bit afraid I broke something. Kinda relieved it's an outside problem. 😅

from server.

Having the same error. Using MariaDB. Going to try and roll back to 204.1.2-beta.

from server.

same issue with postgre 14. The rollback solves the issue

from server.

I also noticed this in the nginx.log

2024/02/08 14:44:39 [emerg] 60#60: open() "/etc/nginx/http.d/bitwarden.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:37
2024/02/08 14:44:40 [emerg] 112#112: open() "/etc/nginx/http.d/bitwarden.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:37
2024/02/08 14:44:43 [emerg] 119#119: open() "/etc/nginx/http.d/bitwarden.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:37
2024/02/08 14:44:46 [emerg] 146#146: open() "/etc/nginx/http.d/bitwarden.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:37

from server.

Unfortunately still seems to be an issue with the now-versioned 2024.2.0-beta

from server.

Yes still have the same issue with the new beta. 2024.2.0-beta

from server.

Tried again with the last beta... same error.

You must install or update .NET to run this application.
App: /usr/local/bin/hbs
Architecture: arm64
Framework: 'Microsoft.NETCore.App', version '6.0.0' (arm64)
.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=arm64&rid=linux-arm64&os=debian.12
2024-02-09 05:19:17,702 INFO Included extra file "/etc/supervisor.d/admin.ini" during parsing
2024-02-09 05:19:17,702 INFO Included extra file "/etc/supervisor.d/api.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/events.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/icons.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/identity.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/nginx.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/notifications.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/scim.ini" during parsing
2024-02-09 05:19:17,703 INFO Included extra file "/etc/supervisor.d/sso.ini" during parsing
2024-02-09 05:19:17,721 INFO RPC interface 'supervisor' initialized
2024-02-09 05:19:17,722 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-02-09 05:19:17,723 INFO supervisord started with pid 1
2024-02-09 05:19:18,727 INFO spawned: 'identity' with pid 55
2024-02-09 05:19:18,732 INFO spawned: 'admin' with pid 56
2024-02-09 05:19:18,738 INFO spawned: 'api' with pid 57
2024-02-09 05:19:18,744 INFO spawned: 'icons' with pid 58
2024-02-09 05:19:18,750 INFO spawned: 'nginx' with pid 59
2024-02-09 05:19:18,757 INFO spawned: 'notifications' with pid 60
2024-02-09 05:19:18,759 WARN exited: identity (exit status 150; not expected)
2024-02-09 05:19:18,762 WARN exited: admin (exit status 150; not expected)
2024-02-09 05:19:18,763 WARN exited: api (exit status 150; not expected)
2024-02-09 05:19:18,772 WARN exited: icons (exit status 150; not expected)
2024-02-09 05:19:18,777 WARN exited: notifications (exit status 150; not expected)
2024-02-09 05:19:18,792 WARN exited: nginx (exit status 1; not expected)
2024-02-09 05:19:19,797 INFO spawned: 'identity' with pid 61
2024-02-09 05:19:19,803 INFO spawned: 'admin' with pid 62
2024-02-09 05:19:19,807 INFO spawned: 'api' with pid 63
2024-02-09 05:19:19,813 INFO spawned: 'icons' with pid 64
2024-02-09 05:19:19,819 INFO spawned: 'nginx' with pid 65
2024-02-09 05:19:19,826 INFO spawned: 'notifications' with pid 66
2024-02-09 05:19:19,828 WARN exited: identity (exit status 150; not expected)
2024-02-09 05:19:19,829 WARN exited: admin (exit status 150; not expected)
2024-02-09 05:19:19,834 WARN exited: api (exit status 150; not expected)
2024-02-09 05:19:19,842 WARN exited: icons (exit status 150; not expected)
2024-02-09 05:19:19,851 WARN exited: nginx (exit status 1; not expected)
2024-02-09 05:19:19,855 WARN exited: notifications (exit status 150; not expected)
2024-02-09 05:19:21,860 INFO spawned: 'identity' with pid 67
2024-02-09 05:19:21,865 INFO spawned: 'admin' with pid 68
2024-02-09 05:19:21,870 INFO spawned: 'api' with pid 69
2024-02-09 05:19:21,875 INFO spawned: 'icons' with pid 70
2024-02-09 05:19:21,881 INFO spawned: 'nginx' with pid 71
2024-02-09 05:19:21,890 INFO spawned: 'notifications' with pid 72
2024-02-09 05:19:21,891 WARN exited: identity (exit status 150; not expected)
2024-02-09 05:19:21,892 WARN exited: admin (exit status 150; not expected)
2024-02-09 05:19:21,897 WARN exited: api (exit status 150; not expected)
2024-02-09 05:19:21,908 WARN exited: notifications (exit status 150; not expected)
2024-02-09 05:19:21,911 WARN exited: icons (exit status 150; not expected)
2024-02-09 05:19:21,913 WARN exited: nginx (exit status 1; not expected)
2024-02-09 05:19:24,923 INFO spawned: 'identity' with pid 73
2024-02-09 05:19:24,932 INFO spawned: 'admin' with pid 74
2024-02-09 05:19:24,941 INFO spawned: 'api' with pid 75
2024-02-09 05:19:24,951 INFO spawned: 'icons' with pid 76
2024-02-09 05:19:24,960 INFO spawned: 'nginx' with pid 77
2024-02-09 05:19:24,985 INFO spawned: 'notifications' with pid 78
2024-02-09 05:19:24,988 WARN exited: identity (exit status 150; not expected)
2024-02-09 05:19:24,999 WARN exited: admin (exit status 150; not expected)
2024-02-09 05:19:25,000 WARN exited: api (exit status 150; not expected)
2024-02-09 05:19:25,015 INFO gave up: identity entered FATAL state, too many start retries too quickly
2024-02-09 05:19:25,016 INFO gave up: admin entered FATAL state, too many start retries too quickly
2024-02-09 05:19:25,017 INFO gave up: api entered FATAL state, too many start retries too quickly
2024-02-09 05:19:25,017 WARN exited: icons (exit status 150; not expected)
2024-02-09 05:19:25,018 INFO gave up: icons entered FATAL state, too many start retries too quickly
2024-02-09 05:19:25,019 WARN exited: notifications (exit status 150; not expected)
2024-02-09 05:19:25,019 INFO gave up: notifications entered FATAL state, too many start retries too quickly
2024-02-09 05:19:25,027 WARN exited: nginx (exit status 1; not expected)
2024-02-09 05:19:26,028 INFO gave up: nginx entered FATAL state, too many start retries too quickly

from server.

I can confirm this error as well upgrading to 2024.2.0-beta:

bitwarden_1 | Adding user bitwarden' to group users' ...
db_1 | 2024-02-10 23:36:14 0 [Note] InnoDB: Buffer pool(s) load completed at 240210 23:36:14
db_1 | 2024-02-10 23:36:14 0 [Note] mariadbd: ready for connections.
db_1 | Version: '10.11.6-MariaDB-1:10.11.6+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
bitwarden_1 | You must install or update .NET to run this application.
bitwarden_1 |
bitwarden_1 | App: /usr/local/bin/hbs
bitwarden_1 | Architecture: x64
bitwarden_1 | Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
bitwarden_1 | .NET location: /usr/share/dotnet
bitwarden_1 |
bitwarden_1 | The following frameworks were found:
bitwarden_1 | 8.0.1 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]
bitwarden_1 |
bitwarden_1 | Learn more:
bitwarden_1 | https://aka.ms/dotnet/app-launch-failed
bitwarden_1 |
bitwarden_1 | To install missing framework, download:
bitwarden_1 | https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=linux-x64&os=debian.12

from server.

It looks like the image is downloading https://github.com/bitwarden/Handlebars.conf/releases/download/v1.3.0/hbs_linux-x64_dotnet.zip

When I download that file, it says it needs .NET 6.
You must install .NET to run this application.

App: /home/shofutex/hbs/hbs
Architecture: x64
App host version: 6.0.10
.NET location: Not found

Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed

Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=ubuntu.22.04-x64&apphost_version=6.0.10

from server.

A lot of the dependencies are still using 6.0 references. It is better to work around it by installing dotnet 6.0 SDK on unified setup as well. This will significantly increase the image size, but it will get the problem solved in the mid-term until we sorted out all the outdated references.

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS legacy-aspnet-6.0
FROM mcr.microsoft.com/dotnet/runtime:6.0 AS legacy-runtime-6.0
FROM bitwarden/self-host:beta
COPY --from=legacy-aspnet-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/host/", "/usr/share/dotnet/host/"]

from server.

Why does it take so long to fix this? Just add .net 6 to the image, even if it is temporary. Can this get some more prio please

You can already do this on your own by making a new image based on my method

from server.

There is a new beta just released and still no joy :/

from server.

A lot of the dependencies are still using 6.0 references. It is better to work around it by installing dotnet 6.0 SDK on unified setup as well. This will significantly increase the image size, but it will get the problem solved in the mid-term until we sorted out all the outdated references.

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS legacy-aspnet-6.0
FROM mcr.microsoft.com/dotnet/runtime:6.0 AS legacy-runtime-6.0
FROM bitwarden/self-host:beta
COPY --from=legacy-aspnet-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/host/", "/usr/share/dotnet/host/"]

What are the exact steps to make a new image based on this method?

from server.

A lot of the dependencies are still using 6.0 references. It is better to work around it by installing dotnet 6.0 SDK on unified setup as well. This will significantly increase the image size, but it will get the problem solved in the mid-term until we sorted out all the outdated references.

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS legacy-aspnet-6.0
FROM mcr.microsoft.com/dotnet/runtime:6.0 AS legacy-runtime-6.0
FROM bitwarden/self-host:beta
COPY --from=legacy-aspnet-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/host/", "/usr/share/dotnet/host/"]

What are the exact steps to make a new image based on this method?

Just put that into a Dockerfile and docker build -t your_image

from server.

A lot of the dependencies are still using 6.0 references. It is better to work around it by installing dotnet 6.0 SDK on unified setup as well. This will significantly increase the image size, but it will get the problem solved in the mid-term until we sorted out all the outdated references.

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS legacy-aspnet-6.0
FROM mcr.microsoft.com/dotnet/runtime:6.0 AS legacy-runtime-6.0
FROM bitwarden/self-host:beta
COPY --from=legacy-aspnet-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/host/", "/usr/share/dotnet/host/"]

What are the exact steps to make a new image based on this method?

Just put that into a Dockerfile and docker build -t your_image

I apologize i'm a beginner with vast amounts of docker options and variables. How then do I include this new image into my docker compose for bitwarden unified? Right now in docker compose i have "image: bitwarden/self-host:beta" under "services" and "bitwarden"

from server.

A lot of the dependencies are still using 6.0 references. It is better to work around it by installing dotnet 6.0 SDK on unified setup as well. This will significantly increase the image size, but it will get the problem solved in the mid-term until we sorted out all the outdated references.

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS legacy-aspnet-6.0
FROM mcr.microsoft.com/dotnet/runtime:6.0 AS legacy-runtime-6.0
FROM bitwarden/self-host:beta
COPY --from=legacy-aspnet-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/shared/", "/usr/share/dotnet/shared/"]
COPY --from=legacy-runtime-6.0 ["/usr/share/dotnet/host/", "/usr/share/dotnet/host/"]

What are the exact steps to make a new image based on this method?

Just put that into a Dockerfile and docker build -t your_image

I apologize i'm a beginner with vast amounts of docker options and variables. How then do I include this new image into my docker compose for bitwarden unified? Right now in docker compose i have "image: bitwarden/self-host:beta" under "services" and "bitwarden"

I think I figured it out myself. I made a file called "Dockerfile" with no extension in the same directory as my docker compose file. I then copied and pasted the code from stevefan1999-personal's post into this file. I then ran the command in the same directory "docker build -t bitwarden-modified:beta ." I had to make sure included a "." after "beta" for docker build to use the Dockerfile in the current directory. I then proceeded to edit my docker compose file to "image: bitwarden-modified:beta" and then start the container with "docker compose up -d" and voila!! It works.

I am assuming I'll have to rebuild this image manually after every update to bitwarden/self-host:beta on dockerhub.

from server.

Still an issue.
I get that its a beta but cant they just throw a dev on there for an workday to either fully add the requirement to the image or change the references to the wrong one?

from server.

Bitwarden committed an update to their hbs library they use a few days ago to update it for .NET 8 and released a new version. That's what led me to test again. bitwarden/Handlebars.conf@6e2a599

from server.

Bitwarden committed an update to their hbs library they use a few days ago to update it for .NET 8 and released a new version. That's what led me to test again. bitwarden/Handlebars.conf@6e2a599

I was confused by your comment are you saying that it is working now after you tested or was it still non-functional for you?

from server.

Bitwarden committed an update to their hbs library they use a few days ago to update it for .NET 8 and released a new version. That's what led me to test again. bitwarden/Handlebars.conf@6e2a599

I was confused by your comment are you saying that it is working now after you tested or was it still non-functional for you?

It was still non-functional, but this time the error was a core dump rather than an error about .NET versions.

from server.

Changing from beta to dev has resolved it for me and everything is working at the moment.

from server.

2024.1.2-beta

Hmm, really hoping they port over the changes from dev to beta then. For the beta tag the .net error has disappeared but now has nginx user issues -_-

from server.

@GitTimeraider Can you elaborate on those nginx user issues you are seeing or link to an existing issue? I am not seeing any problems so just want to see if I can reproduce.

from server.

@Noobstradamus .. basically this. When using the latest beta version (not dev) below happens at me as well. Before U had the .net issue but now I keep having the issue whereby the nginx user started by the container just keeps crashing untill a fatal error.
And this makes it so that its still not usable

As others have mentioned, this specific issue was resolved, but now the issue is #3820

from server.

I just tried the latest "beta" (pushed on Feb 26, 2024 at 1:11 pm).

Issue is still not resolved.

Weird, latest beta works perfectly fine for me. Neither .net nor nginx errors

from server.

Latest beta works for me as well.

from server.

Latest beta works now.

from server.

I just tried the latest "beta" (pushed on Feb 26, 2024 at 1:11 pm).
Issue is still not resolved.

Weird, latest beta works perfectly fine for me. Neither .net nor nginx errors

I agree. I must have done something wrong. It works now.

from server.

Yeah, just reverted back to latest beta and all is working. 👍

from server.

i can confirm that latest :beta works here also.

from server.

Also tried the latest beta on my fly.io instance :) Worked like a charm

from server.

Thanks everyone for your patience and the reports of this being fixed.

Closing this now.

from server.