Your local data is too old to be migrated about vaultwarden HOT 10 CLOSED

Not sure why you are upgrading one version at a time. Just update to the latest version and it should be working.

Just create a backup of you do not trust it. While making backups is always a good idea though.

Also, that error is a client error, which we can't really fix as we do not maintain those.

from vaultwarden.

@BlackDex That is the problem, I just went to the newest and it broke completely. So I went back and did one at a time to find the version it broke in. Anything above 1.30 doesn't work.

What do you mean you don't maintain it? The error I am reporting is at https://vaultwarden.domain.com/#/login (on the hosted page). The page is not loading at all and I am getting the above error.

from vaultwarden.

Clients are not build by Vaultwarden, so the error reported doesn't help really. Vaultwarden is only the server backend.

The error you have might be cache issues of the browser or your reverse proxy maybe. Try a different browser, Incognito/Private mode and check again.

from vaultwarden.

Interesting, where do you get the clients from that I might be able to report this issue? Bitwarden themselves?

I have tried multiple computers, browsers, incognito, etc. Same issue.

from vaultwarden.

It clearly states the local client data is too old. Which would be non existing if you opened it in a private window which should have no prior data and starts all over and nothing to be migrated at all.

from vaultwarden.

The web-vault is build from the official client repo with some small patches to make it work correctly with Vaultwarden. All other clients are the original Bitwarden clients.

from vaultwarden.

Okay, I will reach out to Bitwarden with my error and see what they say.

I know what it states which is why I am very confused that even when I open the site in an incognito window, or a computer which has NEVER used it before, or a brand new browser I just installed, I get the exact same error.

Clearing cache/cookies didn't do anything either.

from vaultwarden.

And what happens with a new account?

Also, i do not think Bitwarden will help at all. 1 this is an older web-vault version. Second you use Vaultwarden for which they do not provide support.

The main issue for me is, this client issue doesn't make sense within a empty browser never used browser. And we are probably not able to reproduce this error at all i think.

from vaultwarden.

I just left it for the day and checked back this morning, now everything is working properly on all systems. Wondering if it was a DNS cache which wasn't clearing causing some kind of issue with miss-matched cached files. Either way it appears to be working now and I also know more about how vaultwarden works. I appreciate all the hard work from the community on this project BTW.

from vaultwarden.

Ah, glad it works now!

Really weird issue.

from vaultwarden.