Also just adding the official help article here.

https://bitwarden.com/help/article/change-client-environment/#browser-extensions-desktop-apps-and-mobile-apps

ps: I also use bitwarden every day, and here is one of my favorite projects to use with bitwarden on a linux client.

https://github.com/mattydebie/bitwarden-rofi

@mazarian thanks for following up!

@necrevistonnezr update was pushed now for 1.22.1

Okay weird update... I changed it to 1G but still received the same error after restarting MySQL service. So then I went back and set it back to 64M default it had (which should have been enough anyways), but then when I tried it again soon after it then suddenly worked importing the JSON file without "Malformed communication packet", it's as if maybe the 1G value worked but wasn't recognized until later? Or it was a total coincidence, I'm not certain which yet. lol.

I'm wondering now if it maybe makes sense to up the max_allowed_packet up a bit though? I mean 64 MB is fine but wondering if it should be closer to 256 MB or something like that instead? I'm not certain if this was even to do with it, but it seemed possible given that it worked soon after tinkering with the values.

Should have been Rustwarden 🙂

@girish
Thanks to both of you!

@scooke said in Bitwarden_rs:

Scaleway Object Storage, where you get 75GB free.

Wow . Never heard of them, but that is a good price.

Wow this is huge! Thanks for the quick update @nebulon !

@timconsidine Thanks for the excellent write up!

@fbartels its a pity - the timeout for locking the session is always set to 15 minutes. right here I would like 5 minutes...

@iamthefij alternately, if the ldap syncer could write the emails to some db field/file and bitwarden_rs can use that as an allow list that would also work.

@fbartels Thanks for the suggestion! Looks like that tool needs the master password every time it performs an action so no automation possible, but still good for periodical manual backups.

@fbartels yep, you're right, I see it listed in the Features Request META issue.

@danigl oh thanks for the heads up, i wonder how we missed the release. I guess since it was over xmas, it somehow got overlooked.

@nebulon said in Why I'm unable to login in my bitwarden ?:

Maybe your Phone is not set to update from network time?

indeed, I just assumed after 6 years that was enabled 🙂
but apparently it wasn't 😳

@girish said in iOS 14.1 can not login, everywhere else works:

@privsec Do you have an app installed on myprivsec.com ? It doesn't look like you have any app installed there? Looks like just the DNS points to the server.

(If it's not clear, when you install an app, leave the location field empty. When you leave the location field empty, it will install the app to myprivsec.com)

Gosh darn it.

Lol.

I did it for a previous issue, and then changed it and then checked the SSL. I will leave this (An app on the bare domain) as the setup currently. Thank you.

@thetomester13 Thanks! Should be fixed now.

@nebulon Ah yes I see what you mean. Let's hope this does the trick. From the changelog: "Now the initial database connection doesn't fail instantly when there's an error, but retries for up to 15 times by default, adjustable with the DB_CONNECTION_RETRIES option."

It now works with the Bitwarden login but not with Amazon - I also contacted Amazon - apparently they have a problem on their side!

I tried on a new instance here and it works. You may have to report that upstream at the bitwarden_rs project. Hopefully they know how to debug this further.

@d19dotca Indeed.

I have reverted the changes and pushed a new package.

Put the notes at https://cloudron.io/documentation/apps/bitwardenrs/#yubikey