mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-16 02:22:14 -05:00
@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.
#4871
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vaultwarden#4871
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @estranged-networks on GitHub (Mar 3, 2022).
@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
/adminfor example and not clutter this topic.Originally posted by @BlackDex in https://github.com/dani-garcia/vaultwarden/discussions/1642#discussioncomment-2283609
@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.