username or access code is incorrect

[Terrorb1ade]

Prerequisites

• I have searched the existing Closed AND Open Issues AND Discussions
• I have searched and read the documentation

Vaultwarden Support String

Sorry to bother you!

I can't use the feature log in with device.

Vaultwarden Build Version

v1.35.8

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

nginx proxy manager v2.14.0

Host/Server Operating System

Linux

Operating System Version

No response

Clients

Browser Extension

Client Version

No response

Steps To Reproduce

  # docker logs -f vaultwarden                                                                                                                                                                                                                                             !49
[2026-04-25 12:19:12.315][vaultwarden::api::identity][ERROR] Username or access code is incorrect. Try again. IP: *. Username: *@gmail.com.
[2026-04-25 12:19:12.315][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2026-04-25 12:19:12.611][vaultwarden::api::notifications][INFO] Closing WS connection from *
[2026-04-25 12:19:12.647][request][INFO] GET /api/auth-requests
[2026-04-25 12:19:12.649][response][INFO] (get_auth_requests) GET /api/auth-requests => 200 OK
[2026-04-25 12:19:12.676][request][INFO] GET /api/devices/knowndevice
[2026-04-25 12:19:12.677][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK

Expected Result

Plz fix the bug with log in with device

Actual Result

Logs

Screenshots or Videos

No response

Additional Context

No response

[BlackDex]

You need to provide a MFA/2FA before you can continue.
Doesn't matter if you use master password or login with device.

I just tested it, and works fine.

Else we need more details.

[Terrorb1ade]

Thank you for replying.

I've confirmed that the server time is perfectly synced via NTP (System clock synchronized: yes).

However, looking at the log Closing WS connection, it happens right before/during the identity token exchange. I am using Nginx Proxy Manager. I suspect the proxy might be closing the connection prematurely during the handshake.

I will try increasing proxy_read_timeout and proxy_send_timeout to see if it stabilizes the "Log in with device" flow. Has anyone else reported issues with NPM's default timeouts and this feature?