When using Adguard home, I randomly get logged out of bitwarden. I thinkt that adguard is blocking something import but I can’t figure out what. The only thing that I see in the query log, is google firebase, but I don’t think that that would be it. What url’s do I need to whitelist?
As a test, I have already done:
@||vault.bitwarden.com^$important
@@||api.bitwarden.com^$important
@@||identity.bitwarden.com^$important
@@||vault.bitwarden.eu^$important
@@||api.bitwarden.eu^$important
@@||identity.bitwarden.eu^$important
This has not worked.
I log into the eu website (I don’t self host bitwarden)
It happens both on my local network as on cellular data, as I use DoH which is always on.
@Minemap Welcome to the forum!
Perhaps Adguard is deleting your session tokens? I would suggest experimenting with any settings that delete cookies or other browser data.
Here is a list of additional URLs that you could try to whitelist:
If the above ideas don’t work, then I would suggest that you contact Customer Support for assistance. They could check if the problem is caused by your IP address being blocked, etc.
Well I just realised that it wasn’t from adguard home, as I just removed it, and the problem is still here. But now I am even more confused. I have no clue what is going on. It’s also only on the ios app. My browser extension works perfectly. I also don’t have to enter in my 2fa after the first time that it kicked me out.
The skipping of 2FA occurs if you enable “Remember me” when logging in a specific device; you can restore the 2FA requirement by going to the Web Vault and deauthorizing all sessions.
In your iOS Bitwarden app, what are your configurations (under Settings > Account Security) for the Timeout Action and Timeout interval?
My timeout interval is: never (I don’t know if this is intended behaviour, but this always gets reset to 15 minutes when I have to log in again)
My timeout action is: lock (not logout, which is happening)
Just found something. It wasn’t adguard home. It’s authentik. I opened the app, it opened logged in. I went to my authentik login page and clicked on my webauthn passkey login button, and it opened the bitwarden login screen when I pressed it. When I go back to the bitwarden app, I am also logged out. Authentik logs me out for whatever reason. But then when I log in, go
back and try it again, now I can use my passkey. Any ideas?
It’s only when I use a passkey, not anything else, and it’s only the passkey for bitwarden that logs me out. All the other passkeys that I have saved work just fine. I use a separate flow for login with a webauthn/passkey, which I setup using a video from the cooptonian, and it works fine, when I am logged into bitwarden. Compatibility mode is enabled.
I just updated the title to reflect that.
1 Like
Compatibility mode voor authentik lijkt niet uit te maken.
“Compatibility mode for authentik doesn’t seem to matter.”
1 Like
Can a developer do something with this? I quickly switched to the main app after it again logged me out, and I got this prompt after logging in:
Error Domain=Data Error Code=3000 “(null)” UserInfo={ErrorMessage=A cipher with the specified ID was not found.}
De bewerking kon niet worden voltooid. (Data Error fout 3000.)
Stack trace:
0 BitwardenShared 0x0000000104c31ea4 __swift_memcpy81_8 + 73732
1 BitwardenShared 0x0000000104a13f29 objectdestroy.13Tm + 11533
2 BitwardenShared 0x00000001049ca699 objectdestroyTm + 1909
3 BitwardenShared 0x0000000104a7c71d __swift_memcpy49_8 + 3541
4 BitwardenShared 0x0000000104dd82b1 __swift_memcpy9_1 + 3017
5 BitwardenShared 0x00000001049ca699 objectdestroyTm + 1909
6 BitwardenShared 0x0000000104fb4589 objectdestroy.23Tm + 22477
7 BitwardenShared 0x00000001049c18d9 __swift_memcpy1_1 + 7933
8 BitwardenShared 0x0000000104db330d block_destroy_helper + 20877
9 BitwardenShared 0x00000001049ca699 objectdestroyTm + 1909
10 libswift_Concurrency.dylib 0x00000001951a9241 7D7AD359-D240-391B-8E01-A01153D84033 + 414273
Binary images:
Bitwarden: 0x0000000104450000
BitwardenShared: 0x00000001049b8000
BitwardenKit: 0x0000000104614000
User ID: efa17191-537c-4973-b624-b1ef0158376b
Versie: 2025.7.0 (2278)
iPhone17,2 
iOS 18.6 
Production
commit: bitwarden/ios/release/2025.07-rc13@dcf1e21893edd0f995fe8c3cafd165e5f7794795
build source: bitwarden/ios/actions/runs/16224435384/attempts/1
Maybe, if you describe your detailed observations in a bug report (“New Issue”) on Github.