Login issue on clients

[AuhNijGnahz]

After update to the latest image, I have encountered login issue on all client-side applications I use, they are: win11 desktop app, chrome extension, ios app.

docker log:
2024-01-07 12:59:00.915][request][INFO] POST /identity/accounts/prelogin
[2024-01-07 12:59:00.915][response][INFO] 404 Not Found

any solutions there?

[BlackDex]

What version of Vaultwarden are you running and what are the client versions?

[KongNan]

I may be experiencing a similar problem. I'm using the service provided by vaultwarden.net, and my client version is 2023.12.1 from the Edge Store (updated 2023-12-20)

[rickywu]

I have the same problem, vaultwarden/server:alpine
Chrome extension is the latest version

I found the reason, vaultwarden/server:alpine got images build in 2years ago, must use vaultwarden/server:1.30.1-alpine or use vaultwarden/server:latest

[BlackDex]

I'm not sure where you see that the server:alpine is build 2 years ago. According to Docker Hub it's 2 months ago.

If you want the latest alpine i would suggest to use latest-alpine, but alpine would work just fine too.

[rickywu]

@BlackDex see this, I reprocuded again, vaultwarden/server:latest got the same problem, I have to specify version number

[BlackDex]

Did you ever do a docker pull vaultwarden/server:alpine in the past two years? Or any other image? Since i see a lot of old images there. Gitea for example updated like 5 days ago, yours is 16months old.

It looks like you never update your images. Just one pull, and done.

[BlackDex]

Ow, wait, you might also be using a docker mirror which isn't updating those images, or causes other issues.

But that is not something we can fix.

[rickywu]

Do you mean docke.io is not updated?

[BlackDex]

docker.io is updated as you can see in my screenshot, as that is coming from docker hub.
Since all other images also seem very outdated on your system, it must be something on your system which doesn't want to pull new images.

[rickywu]

I think this problem caused by old vesion, I see the same error

[kpfleming]

And old versions of Docker may not be able to pull the latest versions of the images. What version of Docker is being used?

[BlackDex]

Ah yes, i almost forgot that.
You need at least v20.10 if i am correct.

[rickywu]

I found the reason, I'm using dsm 7.2 and need config new registry mirror to pull newest image

[Gerardv514]

I’m on dsm 7.2 and I’m working fine. I’ve never had an issue pulling the latest version and when one is released I see it without delay.

Maybe the difference is I’m using the dsm built in container manager, whereas you maybe using a compose file?(or script).

[rickywu]

The same, maybe caused by registry mirror config, I update and use azuer as mirror then works fine