[GH-ISSUE #6242] [PM-29303] Cloudflare Proxy Causing Trust Chain Issues #66214

Closed
opened 2026-05-14 08:05:40 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @crespire on GitHub (Dec 6, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6242

Steps To Reproduce

I'm self hosting via vaultwarden, but this problem has recently cropped up.

I have a vaultwarden instance behind a Cloudflare proxy.
Basically, I get the error:

An error has occured
We couldn't verify the server's certificate. The certificate chain or proxy settings on your device or your Bitwarden server may not be set up correctly.

I don't get this server on the same device when using the web vault, and on other devices I don't get any issues with the official browser extension, so it seems I only have an issue with the Android app.

Expected Result

Be able to log in and do stuff on my mobile app.

Actual Result

Unable to log in.

Screenshots or Videos

No response

Additional Context

Running the latest vaultwarden behind a Cloudflare proxy. SSL Certifcate checkers I've tried (Comodo, and Digicert) both report checkmarks and show the full chain is correctly configured. On Digicert, the only warning is the issuer because my issuer is Cloudflare and not one of their trusted issuers.

This issue recently cropped up, so I think it's been something in November that surfaced this issue.

I've looked around and found github.com/bitwarden/mobile/issues/1657 but it's long since been closed. This is a reference to the first issue, also closed: https://github.com/bitwarden/android/issues/1657

Build Version

Android 2025.11.0 (20967)

What server are you connecting to?

Self hosted

Self-host Server Version

Vaultwarden 1.34.3

Environment Details

Device is a Pixel 7a running the latest OS version (Android 16, build BP3A.251105.015).

Server is running via docker, with all up to date images behind a Caddy reverse proxy.

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @crespire on GitHub (Dec 6, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6242 ### Steps To Reproduce I'm self hosting via vaultwarden, but this problem has recently cropped up. I have a vaultwarden instance behind a Cloudflare proxy. Basically, I get the error: > **An error has occured** > We couldn't verify the server's certificate. The certificate chain or proxy settings on your device or your Bitwarden server may not be set up correctly. I don't get this server on the same device when using the web vault, and on other devices I don't get any issues with the official browser extension, so it seems I only have an issue with the Android app. ### Expected Result Be able to log in and do stuff on my mobile app. ### Actual Result Unable to log in. ### Screenshots or Videos _No response_ ### Additional Context Running the latest vaultwarden behind a Cloudflare proxy. SSL Certifcate checkers I've tried (Comodo, and Digicert) both report checkmarks and show the full chain is correctly configured. On Digicert, the only warning is the issuer because my issuer is Cloudflare and not one of their trusted issuers. This issue recently cropped up, so I think it's been something in November that surfaced this issue. I've looked around and found github.com/bitwarden/mobile/issues/1657 but it's long since been closed. This is a reference to the first issue, also closed: https://github.com/bitwarden/android/issues/1657 ### Build Version Android 2025.11.0 (20967) ### What server are you connecting to? Self hosted ### Self-host Server Version Vaultwarden 1.34.3 ### Environment Details Device is a Pixel 7a running the latest OS version (Android 16, build BP3A.251105.015). Server is running via docker, with all up to date images behind a Caddy reverse proxy. ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bugapp:password-manager labels 2026-05-14 08:05:41 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Dec 6, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-29303

<!-- gh-comment-id:3620807959 --> @bitwarden-bot commented on GitHub (Dec 6, 2025): Thank you for your report! We've added this to our internal board for review. ID: [PM-29303](https://bitwarden.atlassian.net/browse/PM-29303) [PM-29303]: https://bitwarden.atlassian.net/browse/PM-29303?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Author
Owner

@pamperer562580892423 commented on GitHub (Dec 6, 2025):

Another user here.

Steps To Reproduce
I'm self hosting via vaultwarden, but this problem has recently cropped up.
...
Self-host Server Version
Vaultwarden 1.34.3

Some words of advice for you: either try to reproduce your issue with a Bitwarden server - or report this to Vaultwarden. (or both)

<!-- gh-comment-id:3620881506 --> @pamperer562580892423 commented on GitHub (Dec 6, 2025): Another user here. > Steps To Reproduce > I'm self hosting via vaultwarden, but this problem has recently cropped up. > ... > Self-host Server Version > Vaultwarden 1.34.3 Some words of advice for you: either try to reproduce your issue with a Bitwarden server - or report this to Vaultwarden. (or both)
Author
Owner

@crespire commented on GitHub (Dec 6, 2025):

I can at least confirm it's a Cloudflare proxy issue - turning off the proxy resolves my problem.

<!-- gh-comment-id:3621285762 --> @crespire commented on GitHub (Dec 6, 2025): I can at least confirm it's a Cloudflare proxy issue - turning off the proxy resolves my problem.
Author
Owner

@crespire commented on GitHub (Dec 7, 2025):

For those also running into this, there seemed to be some internal issue with SSL certificates issued via CF that was resolved. I think messing with the proxy settings caused a re-issue or I was otherwise already close to renewal, but turning it off and on again seemed to resolve the issue for me.

<!-- gh-comment-id:3622056182 --> @crespire commented on GitHub (Dec 7, 2025): For those also running into this, there seemed to be some internal issue with SSL certificates issued via CF that was resolved. I think messing with the proxy settings caused a re-issue or I was otherwise already close to renewal, but turning it off and on again seemed to resolve the issue for me.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#66214