+1, happens for me too, both on Firefox and Chrome. Web vault and Android application are unaffected.
P.S. I am using Vaultwarden as a server
+1, happens for me too, both on Firefox and Chrome. Web vault and Android application are unaffected.
P.S. I am using Vaultwarden as a server
@Pinkbyte Welcome to the Bitwarden Community Forum!
It seems, you are using an unofficial server software, which is not supported by Bitwarden, as it is an independent product. From time to time, there will be compatibility issues between the official Bitwarden client apps (browser extension, mobile app, desktop app…) and an unofficial server product, when Bitwarden implements changes to its own server software and/or client apps. “…Bitwarden cannot guarantee that official clients will work perfectly with non-official servers.”
(Also due to this - and for other reasons - we recommend using the official Bitwarden server software.)
It is generally not possible for members of the Bitwarden community (users or developers) to help with such issues - and with issues of the unofficial server itself. Please seek support in their community spaces.
If you can replicate your issue on an official Bitwarden server, feel free to open a new thread here.
it seems that with the browser EXTENSION, you are unable to delete an account. You can edit, but not delete.
I feel like I shouldn’t have to use the mobile app or web to delete an account - I should be able to do it from the browser extension (with confirmation, of course).
Please consider adding the ability to delete item(s) using the browser extension.
TIA
@samwathegreat Welcome to the forum!
Could it be you are using Vaultwarden as a server?
Indeed I am! Does that somehow make a difference? Does using vaultwarden server have any other implications I should know about?
I notice that I have no issues deleting from the mobile app even though I’m using vaultwarden server…
TIA
EDIT:
Since I can’t reply to this (closed) thread, I’m editing this post.
Upon researching the relevant vaultwarden issues, it turns out that this was a known report issue that has been fixed in a “testing” release and should be resolved in the next official release of vaultwarden.
For anyone else who encounters this issue…
Thanks for pointing me in the right direction.
@samwathegreat Thanks for your reply! I moved your post into another thread with the exact same topic. Please have a look at the posts above for more info regarding your issue. ![]()