mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Cannot login to Desktop and Mobile clients with Cloudflare ZT Tunnels #1810
Reference in New Issue
Block a user
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?
Originally created by @wendellli99 on GitHub (Dec 21, 2023).
Cannot log in to Desktop and Mobile clients
Desktop and mobile clients stopped being allowed to connect to the server. Users cannot sign in or modify content. This likely happened after an Bitwarden app update. The web client and Chrome extension work fine.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
Install the latest Bitwarden desktop or mobile apps and sign in to a self-hosted Vaultwarden server.
Expected behaviour
Users can use the app as usual.
Actual behaviour
Users cannot sign in or make changes to passwords.
Troubleshooting data
This is the error seen when signing in on desktop and mobile apps.

@BlackDex commented on GitHub (Dec 21, 2023):
Fully logout and back in again to solve this.
@wendellli99 commented on GitHub (Dec 21, 2023):
@BlackDex I tried reinstalling the app, both on mac and iOS. It did not help.
@BlackDex commented on GitHub (Dec 21, 2023):
What do the logs say during these attempts?
Also check your reverse proxy logs
@oliboehm commented on GitHub (Dec 21, 2023):
Same issue with Desktop Client:
Version 2023.12.0
Shell 25.9.1
Renderer 114.0.5735.289
Node 18.15.0
Architecture x64
Vaultwarden Version: 2023.3.0
@BlackDex commented on GitHub (Dec 21, 2023):
You are running an outdated Vaultwarden.
@oliboehm commented on GitHub (Dec 21, 2023):
Good point. Just updated Vaultwarden to Version 2023.10.0 and Desktop Client to Version 2023.23.1.
Firefox Client, which also had the issues, works now. But Desktop Client still does not synchronize.
@BlackDex commented on GitHub (Dec 21, 2023):
Fully logout and back in again, not locking, but logout.
@BlackDex commented on GitHub (Dec 21, 2023):
Thinking about that, it maybe doesn't clear the cache fully.
Might be that still something is in the cache of the application that causes an issue.
@oliboehm commented on GitHub (Dec 21, 2023):
I've done that. But still no sync. Do you know if there is any client log I can check?
Also checked the Bitwarden Android App on my tablet and mobile. Both work.
@BlackDex commented on GitHub (Dec 21, 2023):
There is a developer console option in the desktop app. The same as in Chromium. That shows all the connections and JavaScript items.
Also, are you sure you selected the self-host option?
@zacknewman commented on GitHub (Dec 22, 2023):
What desktop app are you using? If you are not using the Windows 10+ app, then it won't work since only the Windows-flavored desktop app works.
@BlackDex commented on GitHub (Dec 22, 2023):
The desktop apps work just fine. Just some features are platform dependant.
So, you can't only have Webauthn/Fido2 as MFA. All other items work just fine.
@oliboehm commented on GitHub (Dec 22, 2023):
It seems that logout is not the same as shutdown.
I restarted the Bitwarden desktop app and also Windows 11 with, but the client didn't sync. After that, I actively logged out my account and logged in again. Now it works. Thanks for your support and sorry that I hijacked the thread.
@DennyDai commented on GitHub (Dec 22, 2023):
Had same issue after upgrading. Logged out (Chrome on Win11) then re-login, now it works for me.
@wendellli99 commented on GitHub (Dec 22, 2023):
@BlackDex Could you point out where that option is? I could not find it anywhere. I'm using the macOS client from the App Store.
And yes, I did select the self-host option and I'm 100% certain the URL is configured correctly.
@BlackDex commented on GitHub (Dec 22, 2023):
@wendellli99 You should be able to press
F12or go viaView>Toggle developer tools.@wendellli99 commented on GitHub (Dec 23, 2023):
@BlackDex Thank you!

Here are the errors I see. The server never outputted any logs during these failed attempts.
I'm using Cloudflare tunnels, so I am not sure if that has anything to do with it, but I have not touched any tunnel settings recently, and both the web client and the Chrome extension works fine for me.
-1703286282535.log
@BlackDex commented on GitHub (Dec 23, 2023):
What are the Vaultwarden logs? The one you posted are client logs.
@wendellli99 commented on GitHub (Dec 23, 2023):
The Vaultwarden server never outputted any logs during these failed attempts.
@wendellli99 commented on GitHub (Dec 23, 2023):
If it is helpful, I just discovered that the Bitwarden client shows this error when I try to set the custom server URL. I've been using the same URL and it works for the Chrome extension so I don't think the URL is wrong.

So, does it look like a Bitwarden client error now?
@BlackDex commented on GitHub (Dec 23, 2023):
If it didn't outputted anything the request probably didn't got received by Vaultwarden. It might be the reverse proxy which doesn't forward the request or does something else.
@wendellli99 commented on GitHub (Dec 23, 2023):
Problem solved! If you are using Cloudflare ZT Access, make sure to set "HTTP Only" from "Cookie settings" to false. I guess the Bitwarden app recently made a change that requires this setting.