Ayitaka

Results 8 comments of Ayitaka

See also [this issue on the self-hosted repository](https://github.com/bitwarden/self-host/issues/35)

> ![image](https://user-images.githubusercontent.com/50854322/182734510-8d1a8f34-f199-4982-b529-ddb7cfb9aeaf.png) > > The admin dashboard is now showing 2022.8.0 as the latest version, while bitwarden/server shows 2022.6.2 as the latest. This is because the [Bitwarden/server](https://github.com/bitwarden/server) version was bumped...

I am still curious to know the initial reasoning for using "Custom" instead of "Enterprise". I have already tested changing it to Enterprise on my server and, so far, it...

PR #182 contains the same changes I made prior to posting this issue and they have been working fine. Though, forcing the SM class into the Custom plan is interesting,...

@djsmith85 please note this is NOT a duplicate of #4059 and should not be closed as such the way #4067 and #4068 were incorrectly closed. This error is due to...

> I was able to fix the issue by installing the latest `docker-compose` and deleting the old one (which was not installed via `apt`). @SynVisions Would you mind sharing the...

> @MatthieuBarthel I have already do this, but no success Check your docker-compose.yml and make sure there are no duplicate services entries (i.e. mssql, web, attachments, api, identity, nginx, etc)....

In case this is useful to anyone, on Debian 11 (Bullseye) you will get an error (for both certs) when running this, presumably because Debian 11 uses openssl 1.1.1w (Bullseye...