same issue with #3750 which was closed (but the server version is 2.25.0) #1837

Closed
opened 2026-02-05 01:57:24 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @qhgary on GitHub (Feb 1, 2024).

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). 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1837