Bitwarden - Self-hosted password manager
-
@iamthefij I've used your build with fixed emails and ldap and it installed well however I'm not sure how to get in.
Bitwarden asks for email so I supply email corresponding to my Cloudron login and Cloudron's password but it says username or password is invalid. Can you suggest something?
-
@jimcavoli We will take this up next week since we are working on getting 4.2 out this week. Will follow up with @iamthefij on what the status is.
-
@jimcavoli We will take this up next week since we are working on getting 4.2 out this week. Will follow up with @iamthefij on what the status is.
@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. -
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.
-
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.
-
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?
-
@necrevistonnezr You almost never have to use
--allow-selfsignedDoesmy.domain.comhave the correct cert?@girish Yes, the situation is the same with or without "--allow-selfsigned"
BTW I'm on macOS 10.15 -
@necrevistonnezr Can you try using the CLI on the demo cloudron? Like:
cloudron login my.demo.cloudron.iousername and password is cloudron. you can then build and install there. does that entire flow work?
@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 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 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.
-
Just started looking into getting this package published. I also found a related https://github.com/dani-garcia/bitwarden_rs/pull/677 .
@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.
