[GH-ISSUE #2349] @estranged-networks i suggest to start a new discussion with as much as details as you can give like logs, what do you see if you go to `/admin` for example and not clutter this topic. #1233

New issue

Closed

opened 2026-03-03 02:07:20 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:07:20 +03:00

Owner

Originally created by @estranged-networks on GitHub (Mar 3, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2349

@estranged-networks i suggest to start a new discussion with as much as details as you can give like logs, what do you see if you go to /admin for example and not clutter this topic.

Originally posted by @BlackDex in https://github.com/dani-garcia/vaultwarden/discussions/1642#discussioncomment-2283609

Originally created by @estranged-networks on GitHub (Mar 3, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2349 @estranged-networks i suggest to start a new discussion with as much as details as you can give like logs, what do you see if you go to `/admin` for example and not clutter this topic. _Originally posted by @BlackDex in https://github.com/dani-garcia/vaultwarden/discussions/1642#discussioncomment-2283609_

kerem closed this issue

2026-03-03 02:07:20 +03:00

kerem commented

2026-03-03 02:07:21 +03:00

Author

Owner

@estranged-networks commented on GitHub (Mar 3, 2022):

thanks for the heads-ups - sry for the clutter :/ - I ended up working it out in the end . /admin was the same ... Zero info, no key no variables set , so i had a look at the volumes and oddly the container was mapped to a randomly created folder name "/var/lib/docker/volumes/2b857bbaa2c29c134ff6f3bd5e55075e1d10171436d114567" once i restored the pi and not the default bitwarden folder - so Just created a new volume called vaultwarden and copied all the data across and re-mapped - seems ok now - No real issue , just dumb luck with the vols.

@estranged-networks commented on GitHub (Mar 3, 2022): thanks for the heads-ups - sry for the clutter :/ - I ended up working it out in the end . /admin was the same ... Zero info, no key no variables set , so i had a look at the volumes and oddly the container was mapped to a randomly created folder name "/var/lib/docker/volumes/2b857bbaa2c29c134ff6f3bd5e55075e1d10171436d114567" once i restored the pi and not the default bitwarden folder - so Just created a new volume called vaultwarden and copied all the data across and re-mapped - seems ok now - No real issue , just dumb luck with the vols.

kerem referenced this issue

2026-03-03 09:08:57 +03:00

[PR #1234] [MERGED] Log proper namespace in the err!() macro #2919