mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 01:10:09 +03:00
Cannot read properties of null (reading 'iterations') #760
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 @yyhhyyyyyy on GitHub.
As mentioned in the question, I encountered this issue when logging in and using self hosting using the Chrome plugin.
docker logs :
[2023-08-04 03:25:25.202][request][INFO] GET /api/devices/knowndevice
[2023-08-04 03:25:25.202][response][INFO] GET /<p..> [10] (web_files) => 404 Not Found
[2023-08-04 03:25:30.937][request][INFO] POST /identity/accounts/prelogin
[2023-08-04 03:25:30.938][response][INFO] 404 Not Found
Version:
Chrome plugin : 2023.7.0
VW:
docker tag version:1.29.1
docker exec vaultwarden /vaultwarden --version
vaultwarden 1.23.1
@yyhhyyyyyy commented on GitHub:
I don't know why I pulled VW version 1.23.1 old version
The issue has been resolved after I upgraded the vw version to 1.27.0.
docker exec vaultwarden /vaultwarden --version
vaultwarden 1.27.0
@BlackDex commented on GitHub:
@Hui824 the latest version is 1.29.1 currently not 1.27.0
@yyhhyyyyyy commented on GitHub:
Okay, thank you for your help
@yyhhyyyyyy commented on GitHub:
@BlackDex
Why did I use the command to pull down the image version, which is version 1.23.1
docker pull vaultwarden/server:latestThe version I upgraded uses the following command, and the obtained version is 1.27.0
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower -cR vaultwardenMust I use the following command to pull the latest image?
docker pull vaultwarden/server:1.29.1I always use 'latest' to obtain the image
Thank you for your reply
@BlackDex commented on GitHub:
docker pull vaultwarden/server:latestshould have pulled1.29.1not1.27.0.I use watchtower too, but then for
testingbut that works just great.It might be that your Docker version is too old? There were some known issues with older docker versions and newer images.
Once updated to the latest version of docker those should be gone.