# Vaultwarden on Synology not working after upgrade

**URL:** <https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110>\
**Category:** Third Party Help\
**Created:** [November 17, 2023, 7:42pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110 "2023-11-17T19:42:43Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flavio](https://avatars.discourse-cdn.com/v4/letter/f/d07c76/32.png) [@Flavio](https://vaultwarden.discourse.group/u/Flavio)\
**Post date:** [November 17, 2023, 7:42pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/1 "2023-11-17T19:42:43Z")

</div>

Hi.  
I’ve used the Container Manager to upgrade my vaultwarden installation. After the upgrade process was completed, it did not start and this is the error message:

`Start container vaultwarden-server1 failed: {"message":"failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory: unknown"}.`

I’ve noticed that there is no project anymore in the Container Manager - I’ve never paid attention to this, but I guess this is what’s gone missing.  
I’ve tried to set it up anew (create), but it’s failing when I complete the wizard with this error:

`Local port 5151 conflicts with other ports used by other services.`

I went into the CLI of my NAS and with netstat I searched for any service listening on port 5151 - nothing found.  
This is how it looks like:

 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/1/1283de708c32814fa323ceb7eee8156cf92463c0.png)  
 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/1/1db6b047fb2dc56504b875bcbcac754c7bef9705.png)  
And this is the reverse proxy config:  
 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/6/6dc195ce338f3d35e8a2f812ef476e1161762fed.png)

Where am I doing wrong?  
Thanks in advance for your help!  
F.

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [November 17, 2023, 11:20pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/2 "2023-11-17T23:20:31Z")

</div>

If you still have dumb-init in there you were using a very old version.

But basically your problem is the same as described here

> <https://github.com/dani-garcia/vaultwarden/issues/4055>
>
> \<!--
> # ###
> NOTE: Please update to the latest version of vaultwarden be…fore reporting an issue!
> This saves you and us a lot of time and troubleshooting.
> See:
> \* https://github.com/dani-garcia/vaultwarden/issues/1180
> \* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image
> # ###
> \--\>
> 
> \<!--
> Please fill out the following template to make solving your problem easier and faster for us.
> This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them.
> 
> Remember to hide/redact personal or confidential information,
> such as passwords, IP addresses, and DNS names as appropriate.
> \--\>
> 
> \### Subject of the issue
> 
> vaultwarden not starting on armv6
> \### Deployment environment
> 
> \<!--
> =========================================================================================
> Preferably, use the \`Generate Support String\` button on the admin page's Diagnostics tab.
> That will auto-generate most of the info requested in this section.
> =========================================================================================
> \--\>
> 
> 
> 
> 
> \* vaultwarden version: 1.30.0
> 
> 
> \* Install method: docker
> 
> \### Troubleshooting data
> 
> /bin/sh: error while loading shared libraries: libc.so.6: ELF load command address/offset not page-aligned

---

<div class="post-metadata">

**Author:** ![Flavio](https://avatars.discourse-cdn.com/v4/letter/f/d07c76/32.png) [@Flavio](https://vaultwarden.discourse.group/u/Flavio)\
**Post date:** [November 18, 2023, 12:10am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/3 "2023-11-18T00:10:17Z")

</div>

Hi.  
I don’t know which version I was running, but it was for sure at least 1.5 years old.  
As I’m very noob in all this: what (and how) should I now do, to correct the issue?  
I’m not using Portainer.  
I somehow understand that I need to remove something from the configuration - but I don’t know where/what.  
Thanks for your help!  
F.

---

<div class="post-metadata">

**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\
**Post date:** [November 18, 2023, 6:02am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/4 "2023-11-18T06:02:33Z")

</div>

> [@Flavio](#):
>
> what (and how) should I now do, to correct the issue?  
> I’m not using Portainer.

Please read or find the documentation of the tool you are using. Most of us won’t be familiar with it either…

And if you can’t figure it out: maybe you can recreate the setup from scratch with the same `/data` folder?

---

<div class="post-metadata">

**Author:** ![Flavio](https://avatars.discourse-cdn.com/v4/letter/f/d07c76/32.png) [@Flavio](https://vaultwarden.discourse.group/u/Flavio)\
**Post date:** [November 18, 2023, 8:40am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/5 "2023-11-18T08:40:49Z")

</div>

mmmhhh… the “tool” is actually the Container Manager from Synology…  
Anyway: recreating the setup sounds good.  
As long as I don’t remove or do anything with the /data folder, I’m safe not losing anything - correct?

Should I also first export everything from one of my Bitwarden clients - just to be “double-safe”?

---

<div class="post-metadata">

**Author:** ![Flavio](https://avatars.discourse-cdn.com/v4/letter/f/d07c76/32.png) [@Flavio](https://vaultwarden.discourse.group/u/Flavio)\
**Post date:** [November 18, 2023, 9:25am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/6 "2023-11-18T09:25:23Z")

</div>

OK - I somehow solved it.  
I’ve deleted the old container and installed vaultwarden/server-latest again from scratch.  
Now it works.  
I was starting to follow instructions found here: [Synology: Install Vaultwarden With Portainer – Marius Hosting](https://mariushosting.com/synology-install-vaultwarden-with-portainer/)  
Do you suggest to use Portainer, or can I just remove it and continue using Synology’s Container Manager?

---

<div class="post-metadata">

**Author:** ![juanbretti](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/juanbretti/32/959_2.png) [@juanbretti](https://vaultwarden.discourse.group/u/juanbretti)\
**Post date:** [November 18, 2023, 5:30pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/7 "2023-11-18T17:30:42Z")

</div>

I am using the default `Synology Container Manager`, and no problems.

This is the setup I have for the `Container Manager > Container`:

```json
{
   "CapAdd" : null,
   "CapDrop" : null,
   "cmd" : "/start.sh",
   "cpu_priority" : 50,
   "enable_publish_all_ports" : false,
   "enable_restart_policy" : true,
   "enabled" : true,
   "env_variables" : [
      {
         "key" : "PATH",
         "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
      },
      {
         "key" : "ROCKET_PROFILE",
         "value" : "release"
      },
      {
         "key" : "ROCKET_ADDRESS",
         "value" : "0.0.0.0"
      },
      {
         "key" : "ROCKET_PORT",
         "value" : "80"
      },
      {
         "key" : "DEBIAN_FRONTEND",
         "value" : "noninteractive"
      },
      {
         "key" : "SEND_PURGE_SCHEDULE",
         "value" : "0 0 5 31 2 ?"
      },
      {
         "key" : "TRASH_PURGE_SCHEDULE",
         "value" : "0 0 5 31 2 ?"
      },
      {
         "key" : "SMTP_PASSWORD",
         "value" : "EDIT_HERE_your_smtp_password"
      }
   ],
   "exporting" : false,
   "id" : "EDIT_HERE__docker_id_some_hash_",
   "image" : "vaultwarden/server:latest",
   "is_ddsm" : false,
   "is_package" : false,
   "labels" : {
      "org.opencontainers.image.created" : "2023-11-05T23:08:37+00:00",
      "org.opencontainers.image.description" : "Unofficial Bitwarden compatible server written in Rust - 1.30.0",
      "org.opencontainers.image.documentation" : "https://github.com/dani-garcia/vaultwarden/wiki",
      "org.opencontainers.image.licenses" : "AGPL-3.0-only",
      "org.opencontainers.image.revision" : "EDIT_HERE_some_hash_super_long",
      "org.opencontainers.image.source" : "https://github.com/dani-garcia/vaultwarden",
      "org.opencontainers.image.url" : "https://github.com/dani-garcia/vaultwarden",
      "org.opencontainers.image.version" : "1.30.0"
   },
   "links" : [],
   "memory_limit" : 0,
   "name" : "vaultwarden",
   "network" : [
      {
         "driver" : "bridge",
         "name" : "bridge"
      }
   ],
   "network_mode" : "bridge",
   "port_bindings" : [
      {
         "container_port" : 80,
         "host_port" : 8083,
         "type" : "tcp"
      }
   ],
   "privileged" : false,
   "shortcut" : {
      "enable_shortcut" : false,
      "enable_status_page" : false,
      "enable_web_page" : false,
      "web_page_url" : ""
   },
   "use_host_network" : false,
   "version" : 2,
   "volume_bindings" : [
      {
         "host_volume_file" : "EDIT_HERE_/where_are_you_storing_the_files_and_data_base_at_your_nas/vaultwarden",
         "is_directory" : true,
         "mount_point" : "/data",
         "type" : "rw"
      }
   ]
}

```

Notice the `EDIT_HERE_` for adding your personal information.

Here is my setup at `Control Panel > Login Portal > Advanced > Reverse Proxy`:

 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/f/f029600486cb21e105b09e22b84fe71843de87e1.png)

Nothing set on `Web Station`.

And check your firewall, at `Control Panel > Security > Firewall > Edit Rules`.  
Check if the ports of **Vaultwarden** network are open.

 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/9/9e78786493dc69d8968509594e3d3e27e4ab0ea7.png)

Check which ports are being used from:

 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/8/89bc879f98401bd37a202f109e8fe2fa002bdf24.png)

---

<div class="post-metadata">

**Author:** ![tof](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/tof/32/1277_2.png) [@tof](https://vaultwarden.discourse.group/u/tof)\
**Post date:** [November 30, 2023, 7:24am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/8 "2023-11-30T07:24:11Z")

</div>

I have a similar problem on my Synology after upgrading vaultWarden from 1.2.1 to the latest version.

```auto
Start container vaultwarden-server failed: {"message":"failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory: unknown"}.

```

Question : how do you edit this setup ?

> [@juanbretti](#):
>
> This is the setup I have for the `Container Manager > Container`

I found the setup in file: Bitwarden.syno.json

PS: before using vaultwarden, Bitwarden was installed, I change the container on may 21 with same configuration files.

May be it should be good to rebuild my vaultwarden-server from scratch and import a json backup of my passwords. What do you think of that ? (I am still a little bit scared to loose all my data)

```auto
{
   "cap_add" : null,
   "cap_drop" : null,
   "cmd" : "/vaultwarden",
   "cpu_priority" : 50,
   "devices" : null,
   "enable_publish_all_ports" : false,
   "enable_restart_policy" : true,
   "enabled" : false,
   "env_variables" : [
      {
         "key" : "SIGNUPS_ALLOWED",
         "value" : "true"
      },
      {
         "key" : "PATH",
         "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
      },
      {
         "key" : "ROCKET_ENV",
         "value" : "staging"
      },
      {
         "key" : "ROCKET_PORT",
         "value" : "80"
      },
      {
         "key" : "ROCKET_WORKERS",
         "value" : "10"
      }
   ],
   "exporting" : false,
   "id" : "0ef3abf0829084aadadfa2e5341f824cb8af060d83068212f0036a47350da977",
   "image" : "vaultwarden/server:latest",
   "is_ddsm" : false,
   "is_package" : false,
   "links" : [],
   "memory_limit" : 157286400,
   "memory_limit_slider" : 100,
   "name" : "bitwarden",
   "network" : [
      {
         "driver" : "bridge",
         "name" : "bridge"
      }
   ],
   "network_mode" : "bridge",
   "port_bindings" : [
      {
         "container_port" : 3012,
         "host_port" : 2166,
         "type" : "tcp"
      },
      {
         "container_port" : 80,
         "host_port" : 2167,
         "type" : "tcp"
      }
   ],
   "privileged" : false,
   "shortcut" : {
      "enable_shortcut" : false
   },
   "use_host_network" : false,
   "volume_bindings" : [
      {
         "host_volume_file" : "/docker/bitwarden",
         "mount_point" : "/data",
         "type" : "rw"
      }
   ]
}

```

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [November 30, 2023, 7:55am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/10 "2023-11-30T07:55:42Z")

</div>

You need to make sure the entrypoint isn’t overridden by the tool you use to manage the containers.

That entrypoint isn’t there anymore for a long time already.

---

<div class="post-metadata">

**Author:** ![tof](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/tof/32/1277_2.png) [@tof](https://vaultwarden.discourse.group/u/tof)\
**Post date:** [November 30, 2023, 8:03am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/11 "2023-11-30T08:03:29Z")

</div>

This is on Synology and I am using Container Manager. To avoid erasing my datas, I have created a specific folder for the new container and I plan to import the vault from a json backup of original container created a few days ago.

Proceeding like this, Is it possible to loose everything ?

---

<div class="post-metadata">

**Author:** ![juanbretti](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/juanbretti/32/959_2.png) [@juanbretti](https://vaultwarden.discourse.group/u/juanbretti)\
**Post date:** [November 30, 2023, 8:21am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/12 "2023-11-30T08:21:29Z")

</div>

You can try as many things as you want. Just make a backup of all the files inside `"host_volume_file" : "/docker/bitwarden"` and export the container `.json` from the `Container Manager`.

Maybe, is better if you rebuild the Vaultwarden container.  
Take a look at [Using Docker Compose · dani-garcia/vaultwarden Wiki · GitHub](https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose)

---

<div class="post-metadata">

**Author:** ![tof](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/tof/32/1277_2.png) [@tof](https://vaultwarden.discourse.group/u/tof)\
**Post date:** [November 30, 2023, 9:38am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/13 "2023-11-30T09:38:55Z")

</div>

where is host\_volume\_file ?

---

<div class="post-metadata">

**Author:** ![juanbretti](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/juanbretti/32/959_2.png) [@juanbretti](https://vaultwarden.discourse.group/u/juanbretti)\
**Post date:** [November 30, 2023, 10:39am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/14 "2023-11-30T10:39:19Z")

</div>

> [@juanbretti](#):
>
> /docker/bitwarden

Sorry, what I mean, is for you to backup all the files that you have under `/docker/bitwarden` or wherever you have the **Vaultwarden** files. Those files should be on your Synology NAS.

---

<div class="post-metadata">

**Author:** ![Flavio](https://avatars.discourse-cdn.com/v4/letter/f/d07c76/32.png) [@Flavio](https://vaultwarden.discourse.group/u/Flavio)\
**Post date:** [November 30, 2023, 11:08am UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/15 "2023-11-30T11:08:28Z")

</div>

Do as I did: just remove the old vaultwarden container and install the new one. Point to the same directory/path where your database is actually located and you’re good to go.  
This is what I did.  
F.

---

<div class="post-metadata">

**Author:** ![tof](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/tof/32/1277_2.png) [@tof](https://vaultwarden.discourse.group/u/tof)\
**Post date:** [November 30, 2023, 12:38pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/16 "2023-11-30T12:38:19Z")

</div>

I just press action reinit  
And it starts

---

<div class="post-metadata">

**Author:** ![ShadowPulse](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/shadowpulse/32/1237_2.png) [@ShadowPulse](https://vaultwarden.discourse.group/u/ShadowPulse)\
**Post date:** [November 30, 2023, 12:55pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-on-synology-not-working-after-upgrade/3110/17 "2023-11-30T12:55:23Z")

</div>

I’ve actually tried it, and it worked for me, too. Thanks a lot for sharing this method!