Update issue with self-hosted bitwarden

Ask the Community Password Manager
,
1

My “Server Installed” version of bitwarden is 2022.12.0. When I log into the instance I see the following:

" => There is 1 zombie process.

  • Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
    just raised the bar for easy, resilient and secure K8s cluster deployment.

    Secure Kubernetes at the Edge | Ubuntu

2 updates can be applied immediately."

My next step after backing up my bwdata folder was to issue the following commands:

./bitwarden.sh updateself
./bitwarden.sh update

Those commands generated the following response:

"bitwarden.sh version 2022.12.0
Docker version 20.10.22, build 3a2c30b
docker-compose version 1.29.2, build unknown

Update not needed
bitwarden@bitwardenone:~$ "

I’m confused. If the latest version is “Version 2023.1.0” and “2 updates can be applied immediately” as the message I get then why do I get the “Update not needed” response when I run the update command?

Any help is appreciated.

Thanks in advance.

1 Like
2

I have the same issue, one zombie process.
But the most important (I think) It doesn’t update to the last version.

3

The admin portal is now detecting the last version :+1:
I will update it later this day

4

Just as a reminder here for anyone self-hosting.
Typically the self-hosted install will “lag” behind the cloud SaaS offering just a bit, as I’ve seen usually only by a few days to maybe a week at most.

This is to be sure any possible issues or bugs in version upgrades can be resolved prior to offering for self-hosted instances, many of which would be business and enterprise but also the few personal home users. Bitwarden wants to provide a working product, and for all the changes and updates through the years I’ve always had things work :star2: flawlessly :star2:
Which for something as critical as a password manager I consider stability to be up there with security.

You can always check the latest release of the self-host release at GitHub - bitwarden/self-host: Bitwarden’s self-hosted release repository which appears to now show version 2023.1.0 as of ~11:13 UTC Thursday, January 12, 2023
For reference the cloud server repo shows updated to the latest release v2023.1.0 as of ~22:30 UTC Tuesday, January 10, 2023

@bw-admin could we possibly check to confirm that the self-hosted /admin panel pulls version info from the self-hosted repo and not the main server repo?

1 Like
5

This is a message from Ubuntu, there are new updates for your operating system. Since Bitwarden is completely managed by the included bitwarden.sh script, this is probably unrelated.

You should do this:

sudo apt update
sudo apt upgrade

Same goes for the zombie process. This could be a Bitwarden process, but it could also be another problem. Try this: How to find zombie process? - Ask Ubuntu

2 Likes
6

Thanks so much for pointing this out.

I sort of forgot that Bitwarden was running on a Linux host.

Do I need to stop Bitwarden to run updates on the host?

Thanks for the assistance.

7

Thanks for this information.

I did see this notice about version lag but I didn’t think it was referring to self-hosted rather I thought it was referring to another type of installation.

8

This is not necessary. Bitwarden runs isolated inside its Docker containers. If host updates affect Docker or Docker itself is updated, it usually restarts the containers automatically.