github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-12 01:45:56 -05:00
Code Issues 79 Packages Projects Releases 78 Wiki Activity

Version missing from logs #1796

New Issue
Closed
opened 2025-11-07 07:19:15 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-07 07:19:15 -06:00
Owner
Copy Link

Originally created by @dfunkt on GitHub (Dec 9, 2023).

Subject of the issue

Version missing

Deployment environment

  • vaultwarden version:
    Latest one built after commit 8ab2002
  • Install method:
    testing-alpine tag via docker compose

Steps to reproduce

  1. Start Vaultwarden
  2. Check logs

Expected behaviour

Show version number with the latest commit from build time

Actual behaviour

Only "Starting Vaultwarden" shows up

Troubleshooting data

vaultwarden  | /--------------------------------------------------------------------\
vaultwarden  | |                        Starting Vaultwarden
    |
vaultwarden  | |--------------------------------------------------------------------|
vaultwarden  | | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
vaultwarden  | | official channels to report bugs/features, regardless of client.   |
vaultwarden  | | Send usage/configuration questions or feature requests to:
    |
vaultwarden  | |   https://github.com/dani-garcia/vaultwarden/discussions or
    |
vaultwarden  | |   https://vaultwarden.discourse.group/
    |
vaultwarden  | | Report suspected bugs/issues in the software itself at:
    |
vaultwarden  | |   https://github.com/dani-garcia/vaultwarden/issues/new
    |
vaultwarden  | \--------------------------------------------------------------------/
vaultwarden  |
Originally created by @dfunkt on GitHub (Dec 9, 2023). <!-- # ### 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. --> Version missing ### 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: Latest one built after commit 8ab2002 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: testing-alpine tag via docker compose ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> 1. Start Vaultwarden 2. Check logs ### Expected behaviour <!-- Tell us what you expected to happen --> Show version number with the latest commit from build time ### Actual behaviour <!-- Tell us what actually happened --> Only "Starting Vaultwarden" shows up ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> ``` vaultwarden | /--------------------------------------------------------------------\ vaultwarden | | Starting Vaultwarden | vaultwarden | |--------------------------------------------------------------------| vaultwarden | | This is an *unofficial* Bitwarden implementation, DO NOT use the | vaultwarden | | official channels to report bugs/features, regardless of client. | vaultwarden | | Send usage/configuration questions or feature requests to: | vaultwarden | | https://github.com/dani-garcia/vaultwarden/discussions or | vaultwarden | | https://vaultwarden.discourse.group/ | vaultwarden | | Report suspected bugs/issues in the software itself at: | vaultwarden | | https://github.com/dani-garcia/vaultwarden/issues/new | vaultwarden | \--------------------------------------------------------------------/ vaultwarden | ```
GiteaMirror added the bug label 2025-11-07 07:19:15 -06:00
GiteaMirror commented 2025-11-07 07:19:16 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Dec 9, 2023):

Strange indeed. Need to look into this.

@BlackDex commented on GitHub (Dec 9, 2023): Strange indeed. Need to look into this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#1796
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?