Originally created by @peterge1998 on GitHub (Feb 28, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4389
<!--
# ###
NOTE: Please update to the latest version of vaultwarden before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/vaultwarden/issues/1180
* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image
# ###
-->
<!--
Please fill out the following template to make solving your problem easier and faster for us.
This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them.
Remember to hide/redact personal or confidential information,
such as passwords, IP addresses, and DNS names as appropriate.
-->
### Subject of the issue
<!-- Describe your issue here. -->
### Deployment environment
<!--
=========================================================================================
Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab.
That will auto-generate most of the info requested in this section.
=========================================================================================
-->
<!-- The version number, obtained from the logs (at startup) or the admin diagnostics page -->
<!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden -->
<!-- Remember to check if your issue exists on the latest version first! -->
* vaultwarden version: image: "vaultwarden/server:latest"
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method:
Docker compose
* Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) -->
Firefox
* Reverse proxy and version: <!-- if applicable -->
none
* Other relevant details:
### Steps to reproduce
visit http://miprdvaultwarden.company.lan:8060/api/config:
### Expected behaviour
Show the actual version thats displayed on the http://miprdvaultwarden.company.lan:8060/#/login page:
### Actual behaviour
It shows 2023.9.1
### Troubleshooting data
image: "vaultwarden/server:latest"
<!-- gh-comment-id:1969105090 -->
@BlackDex commented on GitHub (Feb 28, 2024):
This works as intended:
https://github.com/dani-garcia/vaultwarden/blob/d6b97090fab5eba429a79c35735a0760b2fa9ee2/src/api/core/mod.rs#L196-L201
See:
https://github.com/dani-garcia/vaultwarden/discussions/4034#discussioncomment-7486742
#4040
#4079
Ah okay, whats the best way to get the current version of vaultwarden then?
<!-- gh-comment-id:1969109920 -->
@peterge1998 commented on GitHub (Feb 28, 2024):
Ah okay, whats the best way to get the current version of vaultwarden then?
It also is there in your current screenshot. See the version within the server path.
<!-- gh-comment-id:1969134789 -->
@BlackDex commented on GitHub (Feb 28, 2024):
It is there already.
It also is there in your current screenshot. See the `version` within the `server` path.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @peterge1998 on GitHub (Feb 28, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4389
Subject of the issue
Deployment environment
Install method:
Docker compose
Clients used:
Firefox
Reverse proxy and version:
none
Other relevant details:
Steps to reproduce
visit http://miprdvaultwarden.company.lan:8060/api/config:
Expected behaviour
Show the actual version thats displayed on the http://miprdvaultwarden.company.lan:8060/#/login page:
Actual behaviour
It shows 2023.9.1
Troubleshooting data
@BlackDex commented on GitHub (Feb 28, 2024):
This works as intended:
https://github.com/dani-garcia/vaultwarden/blob/d6b97090fab5eba429a79c35735a0760b2fa9ee2/src/api/core/mod.rs#L196-L201
See:
https://github.com/dani-garcia/vaultwarden/discussions/4034#discussioncomment-7486742
#4040
#4079
@peterge1998 commented on GitHub (Feb 28, 2024):
Ah okay, whats the best way to get the current version of vaultwarden then?
@BlackDex commented on GitHub (Feb 28, 2024):
It is there already.
It also is there in your current screenshot. See the
versionwithin theserverpath.