github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-05-23 08:32:45 -05:00
Code Issues 307 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #3750] Cannot read properties of null (reading 'iterations') #10473

New Issue
Closed
opened 2026-04-20 13:54:11 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 13:54:11 -05:00
Owner
Copy Link

Originally created by @yyhhyyyyyy on GitHub (Aug 4, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3750

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

Originally created by @yyhhyyyyyy on GitHub (Aug 4, 2023). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3750 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
GiteaMirror commented 2026-04-20 13:54:12 -05:00
Author
Owner
Copy Link

@yyhhyyyyyy commented on GitHub (Aug 4, 2023):

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

<!-- gh-comment-id:1664926894 --> @yyhhyyyyyy commented on GitHub (Aug 4, 2023): 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
GiteaMirror commented 2026-04-20 13:54:13 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Aug 4, 2023):

@Hui824 the latest version is 1.29.1 currently not 1.27.0

<!-- gh-comment-id:1665051324 --> @BlackDex commented on GitHub (Aug 4, 2023): @Hui824 the latest version is 1.29.1 currently not 1.27.0
GiteaMirror commented 2026-04-20 13:54:13 -05:00
Author
Owner
Copy Link

@yyhhyyyyyy commented on GitHub (Aug 4, 2023):

@BlackDex
Why did I use the command to pull down the image version, which is version 1.23.1
docker pull vaultwarden/server:latest

The 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 vaultwarden

Must I use the following command to pull the latest image?
docker pull vaultwarden/server:1.29.1

I always use 'latest' to obtain the image

Thank you for your reply

<!-- gh-comment-id:1665088254 --> @yyhhyyyyyy commented on GitHub (Aug 4, 2023): @BlackDex Why did I use the command to pull down the image version, which is version 1.23.1 `docker pull vaultwarden/server:latest` The 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 vaultwarden` Must I use the following command to pull the latest image? `docker pull vaultwarden/server:1.29.1` I always use 'latest' to obtain the image Thank you for your reply
GiteaMirror commented 2026-04-20 13:54:13 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Aug 4, 2023):

docker pull vaultwarden/server:latest should have pulled 1.29.1 not 1.27.0.
I use watchtower too, but then for testing but 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.

<!-- gh-comment-id:1665123381 --> @BlackDex commented on GitHub (Aug 4, 2023): `docker pull vaultwarden/server:latest` should have pulled `1.29.1` not `1.27.0`. I use watchtower too, but then for `testing` but 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.
GiteaMirror commented 2026-04-20 13:54:14 -05:00
Author
Owner
Copy Link

@yyhhyyyyyy commented on GitHub (Aug 4, 2023):

Okay, thank you for your help

<!-- gh-comment-id:1665137930 --> @yyhhyyyyyy commented on GitHub (Aug 4, 2023): Okay, thank you for your help
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#10473
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?