[GH-ISSUE #3410] [BUG] where the command line versioning is different or missing from the web extension versioning #1559

New issue

Closed

opened 2026-03-03 02:10:14 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 02:10:14 +03:00

Owner

Originally created by @calvin-li-developer on GitHub (Apr 3, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3410

Subject of the issue

Deployment environment

vaultwarden version: 1.28.1

Install method: docker via docker compose up -d
Clients used: web browser extension firefox / edge /chrome
Reverse proxy and version: yes via cloudflare tunnels
MySQL/MariaDB or PostgreSQL version: n/a
Other relevant details:

Steps to reproduce

So I have updated to the latest version of vaultwarden using docker compose pull and docker compose up -d then I checked the version via cli with command docker exec vaultwarden /vaultwarden --version and got version 1.28.1

Expected behaviour

Should show version 1.28.1 for server version on the extension about page.

Actual behaviour

when I checked on firefox extension it still shows 1.28.0 but also when I checked via chrome or edge extension it doesnt display any version after the like server version (thrid party):
Firefox about page:

Edge/Chrome about page:

Troubleshooting data

Originally created by @calvin-li-developer on GitHub (Apr 3, 2023). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3410   ### Subject of the issue  ### Deployment environment     * vaultwarden version: 1.28.1  * Install method: docker via `docker compose up -d` * Clients used:  web browser extension firefox / edge /chrome * Reverse proxy and version:  yes via cloudflare tunnels * MySQL/MariaDB or PostgreSQL version:  n/a * Other relevant details: ### Steps to reproduce  So I have updated to the latest version of vaultwarden using `docker compose pull` and `docker compose up -d` then I checked the version via cli with command `docker exec vaultwarden /vaultwarden --version` and got version 1.28.1 ### Expected behaviour  Should show version 1.28.1 for server version on the extension about page. ### Actual behaviour when I checked on firefox extension it still shows 1.28.0 but also when I checked via chrome or edge extension it doesnt display any version after the like server version (thrid party): Firefox about page: ![firefox extension](https://user-images.githubusercontent.com/65045619/229397584-9933f145-de98-4271-9571-2f00e7c075d0.PNG) Edge/Chrome about page: ![edge-chrome extension](https://user-images.githubusercontent.com/65045619/229397599-1b743d7d-df70-4145-8055-b6a5f721aedd.PNG)  ### Troubleshooting data

kerem closed this issue

2026-03-03 02:10:14 +03:00

kerem commented

2026-03-03 02:10:15 +03:00

Author

Owner

@BlackDex commented on GitHub (Apr 3, 2023):

It's probably cached on the client side.
You can check the version we return by going to https://your.domsin.tld/api/config

@BlackDex commented on GitHub (Apr 3, 2023): It's probably cached on the client side. You can check the version we return by going to `https://your.domsin.tld/api/config`

kerem commented

2026-03-03 02:10:15 +03:00

Author

Owner

@calvin-li-developer commented on GitHub (Apr 3, 2023):

Oddly enough when I reinstall bitwarden extension on firefox it has the same screenshot result has the edge / chrome one.

It's probably cached on the client side. You can check the version we return by going to https://your.domsin.tld/api/config

This does display the correct version of vaultwarden. Thanks for the link.

I guess now i'm not sure if its an issue but it doesn't display version at all for the extension about page.

@calvin-li-developer commented on GitHub (Apr 3, 2023): Oddly enough when I reinstall bitwarden extension on firefox it has the same screenshot result has the edge / chrome one. > It's probably cached on the client side. You can check the version we return by going to `https://your.domsin.tld/api/config` This does display the correct version of vaultwarden. Thanks for the link. I guess now i'm not sure if its an issue but it doesn't display version at all for the extension about page.