[GH-ISSUE #4301] same issue with #3750 which was closed (but the server version is 2.25.0) #1843

New issue

Closed

opened 2026-03-03 02:12:42 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 02:12:42 +03:00

Owner

Originally created by @qhgary on GitHub (Feb 1, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4301

My server side version is 2.25.0 because I pulled with the "latest" label. However, the same issue(same wrong message) occurred when I tried to use bitwarden client side, including browser plugin, android app, etc.
By the way, everything goes well when I pulled the version 1.29.1

I use self-signed certificate and local DNS service， and it goes well with other service， so it should have no problem.

Originally created by @qhgary on GitHub (Feb 1, 2024). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4301 My server side version is 2.25.0 because I pulled with the "latest" label. However, the same issue(same wrong message) occurred when I tried to use bitwarden client side, including browser plugin, android app, etc. By the way, everything goes well when I pulled the version 1.29.1 I use self-signed certificate and local DNS service， and it goes well with other service， so it should have no problem.