@JOduMonT Since 3 weeks there is no new Cloudron Vaultwarden App update.

App Title and Version: Vaultwarden 1.27.0
Package Version: com.github.bitwardenrs@1.11.0
Last updated 26 Dec 2022
https://www.cloudron.io/store/com.github.bitwardenrs.html

Please follow the mysql tasks again. I hope that this process will not be necessary when we get a new Vaultwarden app update.

@nebulon That worked. I had to re-enter my settings/variables, but that's better than an empty file 😉 Thanks to you

@jdaviescoates if anything, it means VW continues to work 🤞

@nebulon I did that.
And I just reckognized that admin/diagnostics broke after that.

I installed the new updated package and changed config.env and now diagnostics shows everything correct.

Bildschirmfoto 2022-11-03 um 16.23.18.png

Thank you for helping out, this is resolved now.

@ApplegateR this Is happen when I try enable retention policy so I am understanding now

I will make sure disable Retention policy for each app back up because I do not want my bill go high. But I found solution I used Coldline storage 90 day so it is help 🙂
And soon we build s3 storage here with raid. I gotta research more often

Thanks for sharing this feature I was unaware of 😄

@jdaviescoates Thank you too. This was the solution I needed.

@BrutalBirdie thanks a lot! I must have read this page with my mind somewhere else 🙂

I have update the package, the web versions seems to be compatible with the backend.

@fbartels oh that's very interesting!

I don't think it is an issue, however essentially the more restrictive setting (Cloudron or app) will hit first. Looking at the changes at vaultwarden, their defaults are a lot more restrictive than the ones we have set in iptables as a generic default.

I also think this makes much sense. Some apps may require more stringent measures others don't. So while having a basic line of defense from the platform, the apps can add on top where applicable, since only they know which routes to protect more and which are for example just public routes which just have to be prevented from a denial of service attack.

@girish Thanks for a quick fix, It's now working

@marcusquinn good call! Was also waiting for this to propagate through Vaultwarden and then Cloudron. Glad it's here now 🙂

@girish thx for the clarification!

@rmdes my premium finally is over at Bitwarden, so I have finally moved to Vaultwarden, both on desktop (firefox) and mobile (bitwarden client) and it just works perfectly, next step : yubikey

@potemkin_ai in my case, as it's turned out, the issue was due to the fact that I created user, but not his mailbox 🙄

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