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
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 -->

I'm not able to reproduce this. You are sure you are logged-in into a Vaultwarden environment?
Yes
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?
@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

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}
```
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.
@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.
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 @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
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
@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?
@Netrvin commented on GitHub (Feb 11, 2022):
Yes

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?
@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.
@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.