I just tested it, and it works fine for me. It imports the history just fine.
CSV files do not contain the history, only the JSON exports.
I also tested the different web-vault versions, but all worked.
So please try it again, and make sure you use the JSON export.
Also, the whole import/export is mostly handled by the clients and not the server. The server just receives multiple vault items which are processed just like a new vault item.
@BlackDex commented on GitHub (Jan 27, 2024):
I just tested it, and it works fine for me. It imports the history just fine.
CSV files do not contain the history, only the JSON exports.
I also tested the different web-vault versions, but all worked.
So please try it again, and make sure you use the JSON export.
Also, the whole import/export is mostly handled by the clients and not the server. The server just receives multiple vault items which are processed just like a new vault item.
@MakeCartWheel any updates? Only updating your post and removing the CSV part doesn't help.
I have tested it with latest and testing tagged images, and it work as it should.
Any more details or updates would be helpful. Else i'm going to close this as not reproducible.
@BlackDex commented on GitHub (Jan 29, 2024):
@MakeCartWheel any updates? Only updating your post and removing the CSV part doesn't help.
I have tested it with `latest` and `testing` tagged images, and it work as it should.
Any more details or updates would be helpful. Else i'm going to close this as not reproducible.
I did some more checking, and password history was not imported in web-vaults before v2023.10.0, which correlates to v1.30.0 of Vaultwarden. So all version of Vaultwarden before v1.30.0 are not able to import password history.
According to the Support string you pasted you should have version v1.30.1 and web-vault v2023.10.0, and thus should work.
The only thing i can think of is that either your reverse proxy or your browser servers an older version.
Try to fully refresh the browser, or clear your browser cache, or restart your reverse proxy.
Going to close this as unable to reproduce.
@BlackDex commented on GitHub (Jan 30, 2024):
I did some more checking, and password history was not imported in web-vaults before v2023.10.0, which correlates to v1.30.0 of Vaultwarden. So all version of Vaultwarden before v1.30.0 are not able to import password history.
According to the Support string you pasted you should have version v1.30.1 and web-vault v2023.10.0, and thus should work.
The only thing i can think of is that either your reverse proxy or your browser servers an older version.
Try to fully refresh the browser, or clear your browser cache, or restart your reverse proxy.
Going to close this as unable to reproduce.
@MakeCartWheel commented on GitHub (Jan 31, 2024):
I checked it twice, on different versions, everything works perfectly, a week ago my colleague and I were looking at the monitor, not understanding why the history was not transferred. the version was latest (1.30.1), It's some kind of magic. Thanks for your time.
@MakeCartWheel commented on GitHub (Jan 31, 2024):
I checked it twice, on different versions, everything works perfectly, a week ago my colleague and I were looking at the monitor, not understanding why the history was not transferred. the version was latest (1.30.1), It's some kind of magic. Thanks for your time.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @MakeCartWheel on GitHub (Jan 27, 2024).
Broken Importing password history from vaultwarden export file
moving from one instance of vaultwarden to other, after exporting from one and importing to another, there is no password history
Steps to reproduce
Expected behaviour
password histroy should be imported correctly
(i see password history details in json files, so problem in importing)
environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: SIGNUPS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN
@BlackDex commented on GitHub (Jan 27, 2024):
I just tested it, and it works fine for me. It imports the history just fine.
CSV files do not contain the history, only the JSON exports.
I also tested the different web-vault versions, but all worked.
So please try it again, and make sure you use the JSON export.
Also, the whole import/export is mostly handled by the clients and not the server. The server just receives multiple vault items which are processed just like a new vault item.
@BlackDex commented on GitHub (Jan 29, 2024):
@MakeCartWheel any updates? Only updating your post and removing the CSV part doesn't help.
I have tested it with
latestandtestingtagged images, and it work as it should.Any more details or updates would be helpful. Else i'm going to close this as not reproducible.
@BlackDex commented on GitHub (Jan 30, 2024):
I did some more checking, and password history was not imported in web-vaults before v2023.10.0, which correlates to v1.30.0 of Vaultwarden. So all version of Vaultwarden before v1.30.0 are not able to import password history.
According to the Support string you pasted you should have version v1.30.1 and web-vault v2023.10.0, and thus should work.
The only thing i can think of is that either your reverse proxy or your browser servers an older version.
Try to fully refresh the browser, or clear your browser cache, or restart your reverse proxy.
Going to close this as unable to reproduce.
@MakeCartWheel commented on GitHub (Jan 31, 2024):
Yeah, sorry about that, I've had busy days.
i will try and response if found something.
@BlackDex commented on GitHub (Jan 31, 2024):
No problem, curious if you find something.
@MakeCartWheel commented on GitHub (Jan 31, 2024):
I checked it twice, on different versions, everything works perfectly, a week ago my colleague and I were looking at the monitor, not understanding why the history was not transferred. the version was latest (1.30.1), It's some kind of magic. Thanks for your time.
@BlackDex commented on GitHub (Jan 31, 2024):
Thanks for checking and reporting back!