Bitwarden - Self-hosted password manager
-
@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
-
@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
-
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.
-
@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 -
@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 If you plan on building apps using a local docker install, that can only be done on linux (not the subsystem), otherwise using a build service (either the app one or cloudron's cloud build service) is good on any system with nodejs support
-
@murgero I'm not a developer, but I have stumbled my way through rough spots before. Just so I understand the workflow.
So lets say I want to deploy the Bitwarden app on my Cloudron instance in production (I don't but let's roll with it for a sec)
I would configure my dev environment (install Nodejs, cloudron-cli, and install Cloudron build service app on the Web Store)
I would clone the app I wanted to play with to my local dev machine, cd into that directory and use the cloudron build command to bush this app to the Cloudron Build Service App?
Lastly use the cloudron install command to install the app on to my production instance.
How close am I to the right answer?Thanks again for taking the time out to help me out. I'm trying to understand this stuff, but it's way out of my swimlane.
-
@will I don't use the build service app because it can delete other apps mistakenly. I use the following process for building my apps (step by step, literally) using a local linux machine with Docker, npm, git, and cloudron-cli.
Just make sure you have a free dockerhub account
git clone https://github.com/mitchellurgero/cloudron-vscode cd cloudron-vscode ## Change as you need! docker build -t dockername/projectname:tagname . docker push dockername/projectname:tagname ## End docker changes cloudron login cloudron install --image dockerhuburl/dockername/projectname:tagname
Example commands when replacing the variables with real items:
git clone https://github.com/murgero/MyApp1-cloudron cd MyApp1-cloudron ## Change as you need! docker build -t murgero/MyApp1:latest . docker push murgero/MyApp1:latest ## End docker changes cloudron login cloudron install --image dockerhuburl/murgero/MyApp1:latest
-
@murgero building is much easier now. when you call
cloudron build
it will ask for the registry to upload to. so you just have to enteryour-username/your-chosen-name-for-the image
, e.g.fbartels/cloudron-bitwardenrs
.cloudron install
will then automatically use this image.@will I am still not a huge believer in the ldap sync and the mysql backend of bitwarden. I have updated my repo to the last version and also picked some smtp things from @iamthefij. Sending invites still does not seem to work, will need to look further into this.
Edit: Managed to fix the issue with sending invites. the value of SMTP_AUTH_MECHANISM needs to be quoted, but when exporting it, these quotes are normally removed. Working and up to date version is in the git repo.