Version Number #696

New Issue

Closed

opened 2026-02-04 22:15:14 +03:00 by OVERLORD · 5 comments

OVERLORD commented 2026-02-04 22:15:14 +03:00

Owner

Copy Link

Originally created by @yodaphone on GitHub (Apr 27, 2020).

Subject of the issue

Even after i do a docker pull with bitwardenrs/server:1.14.2, the version number displays Version 2.13.2 in the application.

What am i doing wrong?

Your environment

• Bitwarden_rs version: 1.14.2

• Install method: Docker compose

Steps to reproduce

# bitwarden
version: '3'

services:
 bitwarden:
  image: bitwardenrs/server:1.14.2
  container_name: bitwarden
  restart: always
  volumes:
      - /opt/bitwarden/data:/data/
  ports:
    - 8088:80
    - 3012:3012
  environment:
    LOG_FILE: '/opt/bitwarden/bitwarden.log'
    LOG_LEVEL: 'debug'
    EXTENDED_LOGGING: 'true'
    WEB_VAULT_ENABLED: 'true'
    WEBSOCKET_ENABLED: 'true'
    WEBSOCKET_PORT: '3012'
    ADMIN_TOKEN: 'XXXXXXXXXXXXXXX'
    SIGNUPS_ALLOWED: 'true'

Originally created by @yodaphone on GitHub (Apr 27, 2020). ### Subject of the issue Even after i do a docker pull with bitwardenrs/server:1.14.2, the version number displays Version 2.13.2 in the application. What am i doing wrong? ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: 1.14.2 <!-- How the server was installed: Docker image / package / built from source --> * Install method: 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 bitwarden_rs? --> ``` # bitwarden version: '3' services: bitwarden: image: bitwardenrs/server:1.14.2 container_name: bitwarden restart: always volumes: - /opt/bitwarden/data:/data/ ports: - 8088:80 - 3012:3012 environment: LOG_FILE: '/opt/bitwarden/bitwarden.log' LOG_LEVEL: 'debug' EXTENDED_LOGGING: 'true' WEB_VAULT_ENABLED: 'true' WEBSOCKET_ENABLED: 'true' WEBSOCKET_PORT: '3012' ADMIN_TOKEN: 'XXXXXXXXXXXXXXX' SIGNUPS_ALLOWED: 'true' ```

OVERLORD closed this issue 2026-02-04 22:15:17 +03:00

OVERLORD commented 2026-02-04 22:15:22 +03:00

Author

Owner

Copy Link

@bohanwood commented on GitHub (Apr 27, 2020):

Maybe not

@bohanwood commented on GitHub (Apr 27, 2020):  Maybe not

OVERLORD commented 2026-02-04 22:15:27 +03:00

Author

Owner

Copy Link

@mqus commented on GitHub (Apr 27, 2020):

@brentybh is right, the version you see in the client(the web interface is also a client) is exactly that, the version of the client. If you want to see if the version of your server is right, you have to take a look at the first output from your server. The version should be there somewhere.

But I think it would be good to show the server version somewhere in the admin interface, too (if it is not shown there already)

@mqus commented on GitHub (Apr 27, 2020): @brentybh is right, the version you see in the client(the web interface is also a client) is exactly that, the version of the *client*. If you want to see if the version of your server is right, you have to take a look at the first output from your server. The version should be there somewhere. But I think it would be good to show the server version somewhere in the admin interface, too (if it is not shown there already)

OVERLORD commented 2026-02-04 22:15:29 +03:00

Author

Owner

Copy Link

@bohanwood commented on GitHub (Apr 28, 2020):

@mqus yeah,

@bohanwood commented on GitHub (Apr 28, 2020): @mqus yeah, 

OVERLORD commented 2026-02-04 22:15:34 +03:00

Author

Owner

Copy Link

@yodaphone commented on GitHub (Apr 28, 2020):

thanks

@yodaphone commented on GitHub (Apr 28, 2020): thanks

OVERLORD commented 2026-02-04 22:15:40 +03:00

Author

Owner

Copy Link

@mqus commented on GitHub (Apr 29, 2020):

Ah right, then it's a matter of packaging. For me it didn't show up because it couldn't detect the version during the package build process in archlinux. I'll fix that.
Thanks for confirming!

@mqus commented on GitHub (Apr 29, 2020): Ah right, then it's a matter of packaging. For me it didn't show up because it couldn't detect the version during the package build process in archlinux. I'll fix that. Thanks for confirming!

OVERLORD referenced this issue 2026-02-05 04:55:42 +03:00

[PR #696] [CLOSED] Compile sqlite version by default #2756

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#696