starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Latest Bitwarden client 1.31.0 no longer appears as a premium account #1213

New Issue
Closed
opened 2026-02-05 00:17:50 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 00:17:50 +03:00
Owner
Copy Link

Originally created by @Netrvin on GitHub (Feb 11, 2022).

Subject of the issue

Latest Bitwarden client 1.31.0 no longer appears as a premium account
Although attachments and TOTP functions are not affected, it will prompt you not to be a premium account when operating attachments.

Deployment environment

  • vaultwarden version: 1.24.0

  • Install method: Docker image

  • Clients used: Desktop(Windows) 1.31.0

  • Reverse proxy and version: Nginx

  • MySQL/MariaDB or PostgreSQL version: No

  • Other relevant details: No

Steps to reproduce

Click Account -> Premium Membership

Expected behaviour

Appears as a premium account as before

Actual behaviour

"You are not currently a premium member." appeared.

Troubleshooting data

Snipaste_2022-02-11_20-40-54

Originally created by @Netrvin on GitHub (Feb 11, 2022). <!-- # ### 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. --> Latest Bitwarden client 1.31.0 no longer appears as a premium account Although attachments and TOTP functions are not affected, it will prompt you not to be a premium account when operating attachments. ### 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: 1.24.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker image * Clients used: Desktop(Windows) 1.31.0 * Reverse proxy and version: Nginx * MySQL/MariaDB or PostgreSQL version: No * Other relevant details: No ### 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? --> Click Account -> Premium Membership ### Expected behaviour <!-- Tell us what you expected to happen --> Appears as a premium account as before ### Actual behaviour <!-- Tell us what actually happened --> "You are not currently a premium member." appeared. ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> ![Snipaste_2022-02-11_20-40-54](https://user-images.githubusercontent.com/11222509/153593131-00f9f709-012d-44f5-9475-77b01282f5d2.png)
OVERLORD commented 2026-02-05 00:17:56 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Feb 11, 2022):

I'm not able to reproduce this. You are sure you are logged-in into a Vaultwarden environment?

@BlackDex commented on GitHub (Feb 11, 2022): I'm not able to reproduce this. You are sure you are logged-in into a Vaultwarden environment?
OVERLORD commented 2026-02-05 00:18:02 +03:00
Author
Owner
Copy Link

@Netrvin commented on GitHub (Feb 11, 2022):

I'm not able to reproduce this. You are sure you are logged-in into a Vaultwarden environment?

Yes
Snipaste_2022-02-11_21-01-11

I used devtools to check the request made when the refresh button on the premium account panel is pressed, the following is the response, is there any problem?

{"Kdf":0,"KdfIterations":100000,"Key":"xxx","PrivateKey":"xxx","ResetMasterPassword":false,"access_token":"xxx","expires_in":7200,"refresh_token":"xxx","scope":"api offline_access","token_type":"Bearer","unofficialServer":true}
@Netrvin commented on GitHub (Feb 11, 2022): > I'm not able to reproduce this. You are sure you are logged-in into a Vaultwarden environment? Yes ![Snipaste_2022-02-11_21-01-11](https://user-images.githubusercontent.com/11222509/153596276-c2092700-307f-4148-9a76-991ac9f3f280.png) I used devtools to check the request made when the refresh button on the premium account panel is pressed, the following is the response, is there any problem? ``` {"Kdf":0,"KdfIterations":100000,"Key":"xxx","PrivateKey":"xxx","ResetMasterPassword":false,"access_token":"xxx","expires_in":7200,"refresh_token":"xxx","scope":"api offline_access","token_type":"Bearer","unofficialServer":true} ```
OVERLORD commented 2026-02-05 00:18:09 +03:00
Author
Owner
Copy Link

@Netrvin commented on GitHub (Feb 11, 2022):

I try to download the client from the official website again. And the version is 1.30.0. It remains 1.30.0 after checking update. So...I guess I was updated with a new version of the client that has been withdrawn? It feels weird...
The problem doesn't appear in 1.30.0.

@Netrvin commented on GitHub (Feb 11, 2022): I try to download the client from the official website again. And the version is 1.30.0. It remains 1.30.0 after checking update. So...I guess I was updated with a new version of the client that has been withdrawn? It feels weird... The problem doesn't appear in 1.30.0.
OVERLORD commented 2026-02-05 00:18:19 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Feb 11, 2022):

I have version v1.31.0, and no issues with that.
But, it looks like it is a Bitwarden Desktop issue: https://github.com/bitwarden/desktop/issues/1320
Nothing we can do on our side i think.

@BlackDex commented on GitHub (Feb 11, 2022): I have version v1.31.0, and no issues with that. But, it looks like it is a Bitwarden Desktop issue: https://github.com/bitwarden/desktop/issues/1320 Nothing we can do on our side i think.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1213
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?