Bitwarden - Self-hosted password manager

[iamthefij]

@girish it should be good to go. My branch is working with MySQL and LDAP.

I've got two working Dockerfiles. One that compiles the entire project and another that just pulls the binary from the published images on Docker Hub. End result is the same.

[lukaszj]

Hello @girish is there any progress with releasing Bitwarden to App Store? Thanks!

[girish]

Unfortunately, not this week. The 4.2 release hit some hiccups. Good news is that we are rolling out 4.2 as we speak. So, we should get to this next week.

[lukaszj]

@girish Great, can't wait. Fingers crossed!

[iamthefij]

@girish great to hear! Let me know if there is anything I can do to help.

[necrevistonnezr]

Again, there's trouble with cloudron cli. I tried to login but it gives me the following errors:

cloudron login --allow-selfsigned
Cloudron Admin Domain: my.domain.com
ERROR (node:51749) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification. [ internal/process/warning.js:27:3 ]
ERROR Cloudron my.domain.com not found.
Try providing the admin location, probably my.my.domain.com [ /Users/user/.nvm/versions/node/v12.7.0/lib/node_modules/cloudron/src/helper.js:71:29 ]

What am I doing wrong?

[girish]

@necrevistonnezr You almost never have to use --allow-selfsigned Does my.domain.com have the correct cert?

[necrevistonnezr]

@girish Yes, the situation is the same with or without "--allow-selfsigned"
BTW I'm on macOS 10.15

[girish]

@necrevistonnezr Can you try using the CLI on the demo cloudron? Like:

cloudron login my.demo.cloudron.io

username and password is cloudron. you can then build and install there. does that entire flow work?

[necrevistonnezr]

@girish that gives me the same error but pinging works

bitwardenrs-app on master [!?] via ⬢ v12.7.0
➜ cloudron login my.cloudron.io
ERROR (node:55034) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification. [ internal/process/warning.js:27:3 ]
ERROR Cloudron my.cloudron.io not found.
Try providing the admin location, probably my.my.cloudron.io [ /Users/kdj/.nvm/versions/node/v12.7.0/lib/node_modules/cloudron/src/helper.js:71:29 ]
bitwardenrs-app on master [!?] via ⬢ v12.7.0 took 18s
➜ ping my.cloudron.io
PING my.cloudron.io (45.55.2.141): 56 data bytes
64 bytes from 45.55.2.141: icmp_seq=0 ttl=50 time=188.063 ms
64 bytes from 45.55.2.141: icmp_seq=1 ttl=50 time=181.041 ms
64 bytes from 45.55.2.141: icmp_seq=2 ttl=50 time=237.531 ms

[lukaszj]

Hi @girish is there any update re pushing official Bitwarden to Marketplace? Thanks.

[girish]

@lukaszj No ETA but it's on our immediate list. Currently, we are pushing out the release that makes it possible to build custom apps without our build service.

[lukaszj]

@girish Thanks.

[murgero]

@girish But building apps without the build service is already possible - do you mean that the manifest will allow us to specify a repo and docker image to install? Cause that would be nice!

[girish]

Just started looking into getting this package published. I also found a related https://github.com/dani-garcia/bitwarden_rs/pull/677 .

[iamthefij]

@girish I'd be neat if that gets merged, but the maintainers rejected a previous patch for direct LDAP support and that's why it was moved to a different binary. See comments here: https://github.com/dani-garcia/bitwarden_rs/pull/396#issuecomment-464059020

[iamthefij]

Hey @girish any updates on this? I've been holding off on migrating from my external instance to my Cloudron one because I'm not sure about the process of migrating from the dev one to an official one. Any guidance on when to expect this or if it's possible to preserve the Docker volume would be helpful.

[will]

@iamthefij said in Bitwarden - Self-hosted password manager:

Hey @girish any updates on this? I've been holding off on migrating from my external instance to my Cloudron one because I'm not sure about the process of migrating from the dev one to an official one. Any guidance on when to expect this or if it's possible to preserve the Docker volume would be helpful.

I'm in the same boat. I am maintaining a VPS solely for Bitwarden access. Would save $10 a month and time if I could roll this out! Thanks for all the hard work!

I tried deploying the Cloudron Bitwarden like below:

Commands run on Cloudron server.

git clone https://git.cloudron.io/fbartels/bitwardenrs-app #Successfully clones to home directory
npm install -g cloudron-cli **#Command fails, no cloudron-cli **
cloudron build # this will ask your cloudron.io login #Never got to this stage
cloudron install # this will ask you for your cloudron's login #Never got to this stage

[murgero]

@will Those commands do NOT get ran on the cloudron server.

The cloudron CLI is ONLY for use outside of the server (it's the management tool for cli users)

At home, install virtualbox on your computer and create an ubuntu VM. (If you already have a computer with linux, ignore this step, these steps can be installed in windows if you install nodejs and git first)

Then run:

git clone https://git.cloudron.io/fbartels/bitwardenrs-app
cd bitwardenrs-app
## Install NodeJS from https://nodejs.org/en/download/package-manager/
npm install -g cloudron
cloudron build
cloudron install

[will]

@murgero Thanks! I'm running windows subsystem for linux so I'll give it a shot. Thanks again!