starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-02 22:57:18 -05:00

error: cannot decrypt after pulling latest image #115

New issue

Closed

opened 2026-02-20 07:59:27 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-20 07:59:27 -05:00

Owner

Originally created by @themightychris on GitHub (Oct 24, 2018).

When I pull the latest image, I see an error along the lines of "cannot decrypt" in place of every item's title. Luckily, reverting back to image e1509df9617a fixes the problem. Is there some kind of upgrade/migration step that needs to be done? All I could find in the readme was preserving the /data mount between upgrades

Originally created by @themightychris on GitHub (Oct 24, 2018). When I pull the latest image, I see an error along the lines of "cannot decrypt" in place of every item's title. Luckily, reverting back to image `e1509df9617a` fixes the problem. Is there some kind of upgrade/migration step that needs to be done? All I could find in the readme was preserving the /data mount between upgrades

deekerman

2026-02-20 07:59:27 -05:00

closed this issue
added the
troubleshooting
label

deekerman commented

2026-02-20 07:59:28 -05:00

Author

Owner

@mprasil commented on GitHub (Oct 24, 2018):

This is certainly weird. I haven't encountered that and I'm using latest image.

Do you have server logs from after the update? Do you use any proxy or websockets or any extra configuration?

Edit: to answer your question, there's no upgrade step, just pulling latest image should work.

@mprasil commented on GitHub (Oct 24, 2018): This is certainly weird. I haven't encountered that and I'm using latest image. Do you have server logs from after the update? Do you use any proxy or websockets or any extra configuration? Edit: to answer your question, there's no upgrade step, just pulling latest image should work.

deekerman commented

2026-02-20 07:59:28 -05:00

Author

Owner

@themightychris commented on GitHub (Oct 24, 2018):

I have nginx in front of the container, but that remained constant between my original state, pulling the latest image, and then switching back to the original image

Where would I find the relevant server logs? I do not see anything under /data or /var/log within the container and did not find anything on logs in the README

I'm launching my instance with this docker-compose.yml currently:

version: "2"

services:
  web:
    image: e1509df9617a
    restart: always
    environment:
      - SERVER_ADMIN_EMAIL=chris@example.org
    volumes:
      - ./data:/data
    ports:
      - "127.0.0.1:9280:80"

If you can point me where to look for the interesting diagnostic data, I can give it another try and see what I can collect

@themightychris commented on GitHub (Oct 24, 2018): I have nginx in front of the container, but that remained constant between my original state, pulling the latest image, and then switching back to the original image Where would I find the relevant server logs? I do not see anything under `/data` or `/var/log` within the container and did not find anything on logs in the README I'm launching my instance with this `docker-compose.yml` currently: ```yaml version: "2" services: web: image: e1509df9617a restart: always environment: - SERVER_ADMIN_EMAIL=chris@example.org volumes: - ./data:/data ports: - "127.0.0.1:9280:80" ``` If you can point me where to look for the interesting diagnostic data, I can give it another try and see what I can collect

deekerman commented

2026-02-20 07:59:29 -05:00

Author

Owner

@Toucan-Sam commented on GitHub (Oct 25, 2018):

Related to #228 ? :)

I'm not able to pull that image to test if it also solves my problem. Not cool enough?

@Toucan-Sam commented on GitHub (Oct 25, 2018): Related to #228 ? :) I'm not able to pull that image to test if it also solves my problem. Not cool enough?

deekerman commented

2026-02-20 07:59:29 -05:00

Author

Owner

@mprasil commented on GitHub (Oct 25, 2018):

@themightychris , I see you're using SERVER_ADMIN for a user. Is that the user that can't decrypt?

As for the logs, just check the docker logs, bitwarden_rs logs to stdout.

@mprasil commented on GitHub (Oct 25, 2018): @themightychris , I see you're using SERVER_ADMIN for a user. Is that the user that can't decrypt? As for the logs, just check the docker logs, bitwarden_rs logs to stdout.

deekerman commented

2026-02-20 07:59:29 -05:00

Author

Owner

@themightychris commented on GitHub (Oct 25, 2018):

@mprasil yes I added that at the same time I pulled, but left it in when I reverted the image and restored functionality. Was that a new option and you're thinking it could cause problems applied to an existing user?

@themightychris commented on GitHub (Oct 25, 2018): @mprasil yes I added that at the same time I pulled, but left it in when I reverted the image and restored functionality. Was that a new option and you're thinking it could cause problems applied to an existing user?

deekerman commented

2026-02-20 07:59:29 -05:00

Author

Owner

@mprasil commented on GitHub (Oct 25, 2018):

Yes, that is a new feature. Also see the docs, never use the SERVER_ADMIN user for anything else than server administration otherwise you'll have a lot of weird issues. 😄 Apologies for that, but that functionality is kinda hack to give users some way to manage on-server users without creating complete admin interface, so it does break Vault as it's very non-standard. Hence the advice to never use the admin user for anything else and just dedicate it to administration.

@mprasil commented on GitHub (Oct 25, 2018): Yes, that is a new feature. Also see the docs, never use the `SERVER_ADMIN` user for anything else than server administration otherwise you'll have a lot of weird issues. :smile: Apologies for that, but that functionality is kinda hack to give users some way to manage on-server users without creating complete admin interface, so it does break Vault as it's very non-standard. Hence the advice to never use the admin user for anything else and just dedicate it to administration.

deekerman commented

2026-02-20 07:59:29 -05:00

Author

Owner

@themightychris commented on GitHub (Oct 26, 2018):

thanks for the quick help @mprasil ! I'm all set now with the latest version again and a working admin account

@themightychris commented on GitHub (Oct 26, 2018): thanks for the quick help @mprasil ! I'm all set now with the latest version again and a working admin account

deekerman commented

2026-02-20 07:59:29 -05:00

Author

Owner

@mprasil commented on GitHub (Oct 26, 2018):

Great to hear! I think the documentation needs to be a bit more specific about using the admin account. Right now it sounds more like gentle suggestion to not to use that account for anything else, but in reality you should never do this..

@mprasil commented on GitHub (Oct 26, 2018): Great to hear! I think the documentation needs to be a bit more specific about using the admin account. Right now it sounds more like gentle suggestion to not to use that account for anything else, but in reality you should never do this..