# Admin diagnostics reports wrong web-vault version (shows latest instead of compiled version) **URL:** \ **Category:** Help\ **Created:** [October 22, 2025, 1:44pm UTC](https://vaultwarden.discourse.group/t/admin-diagnostics-reports-wrong-web-vault-version-shows-latest-instead-of-compiled-version/4872 "2025-10-22T13:44:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![u550WwH3WFJm](https://avatars.discourse-cdn.com/v4/letter/u/bc8723/32.png) [@u550WwH3WFJm](https://vaultwarden.discourse.group/u/u550WwH3WFJm)\ **Post date:** [October 22, 2025, 1:44pm UTC](https://vaultwarden.discourse.group/t/admin-diagnostics-reports-wrong-web-vault-version-shows-latest-instead-of-compiled-version/4872/1 "2025-10-22T13:44:52Z")
Hello, I’ve encountered a mismatch between the web-vault version shown in the admin diagnostics page and the version actually built and deployed. Setup details: Vaultwarden deployment type: Docker Compose Web-vault source: Built manually from dani-garcia/bw\_web\_builds Vaultwarden version: vaultwarden/server:1.34.3 Web-vault version targeted: v2025.7.0 Steps to reproduce: Clone and build the web-vault: git clone [GitHub - dani-garcia/bw\_web\_builds: Web vault builds for vaultwarden](https://github.com/dani-garcia/bw_web_builds.git) cd bw\_web\_builds git checkout v2025.7.0 make checkout # (when prompted, entered: v2025.7.0) make build make tar Update the Docker Compose volume mapping to use the built vault: volumes: - ./bw\_web\_builds/builds/bw\_web\_v2025.7.0.1:/web-vault:ro Restart Vaultwarden: docker compose -f /opt/vaultwarden/compose.yaml up -d Observed behavior Accessing myvaultdomain.tld/admin/diagnostics → Version reported: 2025.9.1 (latest available) Accessing myvaultdomain.tld → Footer shows v2025.7.0, which matches the version built Expected behavior Both the admin diagnostics page and the web-vault footer should report the same version (v2025.7.0). Additional notes No cache or CDN is involved. Containers were rebuilt from scratch. The mismatch appears to come from the scripts/build\_web\_vault.sh which query GitHub upstream version reference rather than the locally served web vault. ![vw-version-json](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/0/00d7d2ed35cc8f3903f2c3fb0b81e12bba15ef34.png) Questions Is the “Web Installed” version in /admin/diagnostics expected to always show the latest available web vault version (from upstream), regardless of what’s locally deployed? Or is this a bug / misconfiguration when using a custom-built web vault? Thanks in advance for clarifying how this version reporting is intended to work! ---
**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\ **Post date:** [October 22, 2025, 3:31pm UTC](https://vaultwarden.discourse.group/t/admin-diagnostics-reports-wrong-web-vault-version-shows-latest-instead-of-compiled-version/4872/2 "2025-10-22T15:31:23Z")
The footer probably shows the version in `/web-vault/version.json` while the admin shows the one from `/web-vault/vw-version.json`(if it exists). I think the assumption with the latter is that you only build the latest web-vault and not earlier versions. The easiest fix for you would be to remove the `vw-version.json` file from your web-vault. So yes, you could consider that behavior a bug in our build script that should have used the git tag instead. (But even if we changed that now it would not work for older versions of the build script. You’d would have to build it with `VAULT_VERSION=v2025.7.0 make full` instead.) I think it would be fine to not get the latest releases and just use the version string that’s using the `package.json`. The proper fix (for future versions) could be to update the web-vault’s `package.json` to match Vaultwarden’s release but I can’t from the top of my head say if that would break anything where a version check is used by the web-vault expecting the upstream `CalVer` format without any additional letters (e.g. ` v2024.6.2c`). Personally I think that we could probably get rid of this separate repository with the build scripts entirely and move the build logic for the web-vault to the main `vaultwarden` repository so that it can keep track of the version of the `vw_web_builds` repo instead of having to rely on a built web-vault that’s stored in a docker image. But no idea what the best approach to that would be. (I mean ideally I’d also like the web-vault to be able to be built reproducibly so that you can check that the one that is shipped in the vaultwarden container image was not altered but that’s a bit off topic.) ---
**Author:** ![u550WwH3WFJm](https://avatars.discourse-cdn.com/v4/letter/u/bc8723/32.png) [@u550WwH3WFJm](https://vaultwarden.discourse.group/u/u550WwH3WFJm)\ **Post date:** [October 23, 2025, 8:18am UTC](https://vaultwarden.discourse.group/t/admin-diagnostics-reports-wrong-web-vault-version-shows-latest-instead-of-compiled-version/4872/3 "2025-10-23T08:18:29Z")
Thanks for the detailed explanation! Removing vw-version.json solved the issue.