Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Vaultwarden
  3. Bitwarden_rs

Bitwarden_rs

Scheduled Pinned Locked Moved Solved Vaultwarden
51 Posts 16 Posters 7.9k Views 14 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • iamthefijI iamthefij

      @d19dotca The high level will be to do a sql dump of the database and then restore it on the new system.

      d19dotcaD Offline
      d19dotcaD Offline
      d19dotca
      wrote on last edited by
      #24

      @iamthefij Yes, I agree. Though the attachments aren't in the sqlite DB itself, are they? I assume there's a directory we need to bring over too.

      --
      Dustin Dauncey
      www.d19.ca

      necrevistonnezrN 1 Reply Last reply
      0
      • necrevistonnezrN Offline
        necrevistonnezrN Offline
        necrevistonnezr
        wrote on last edited by
        #25

        A simple export from the earlier bitwardn app (courtesy of @fbartels) and import into this app did not work for me:

        Apr 24 09:41:40 172.18.0.1 - - [24/Apr/2020:07:41:40 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"
        Apr 24 09:41:43 [2020-04-24 07:41:43][request][INFO] POST /api/ciphers/import
        Apr 24 09:41:43 [2020-04-24 07:41:43][response][INFO] POST /api/ciphers/import (post_ciphers_import) => 400 Bad Request
        Apr 24 09:41:43 172.18.0.1 - - [24/Apr/2020:07:41:43 +0000] "POST /api/ciphers/import HTTP/1.1" 400 1521 "https://bit.domain.tld/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:76.0) Gecko/20100101 Firefox/76.0"
        Apr 24 09:41:50 172.18.0.1 - - [24/Apr/2020:07:41:50 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"
        
        scookeS 1 Reply Last reply
        0
        • d19dotcaD d19dotca

          @iamthefij Yes, I agree. Though the attachments aren't in the sqlite DB itself, are they? I assume there's a directory we need to bring over too.

          necrevistonnezrN Offline
          necrevistonnezrN Offline
          necrevistonnezr
          wrote on last edited by
          #26

          @d19dotca said in Bitwarden_rs:

          @iamthefij Yes, I agree. Though the attachments aren't in the sqlite DB itself, are they? I assume there's a directory we need to bring over too.

          In both cases, attachments are located in app/data/attachments with unique identifiers as filenames. I don't know if those UIDs remain the same after an export/import (which currenlty fails, see above)

          1 Reply Last reply
          0
          • necrevistonnezrN necrevistonnezr

            A simple export from the earlier bitwardn app (courtesy of @fbartels) and import into this app did not work for me:

            Apr 24 09:41:40 172.18.0.1 - - [24/Apr/2020:07:41:40 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"
            Apr 24 09:41:43 [2020-04-24 07:41:43][request][INFO] POST /api/ciphers/import
            Apr 24 09:41:43 [2020-04-24 07:41:43][response][INFO] POST /api/ciphers/import (post_ciphers_import) => 400 Bad Request
            Apr 24 09:41:43 172.18.0.1 - - [24/Apr/2020:07:41:43 +0000] "POST /api/ciphers/import HTTP/1.1" 400 1521 "https://bit.domain.tld/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:76.0) Gecko/20100101 Firefox/76.0"
            Apr 24 09:41:50 172.18.0.1 - - [24/Apr/2020:07:41:50 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"
            
            scookeS Offline
            scookeS Offline
            scooke
            wrote on last edited by
            #27

            @necrevistonnezr I had similar (the same?) errors and ended up exporting portions of the db and importing said portions, like only the As, then the Bs, etc. Then the importing worked.

            A life lived in fear is a life half-lived

            1 Reply Last reply
            0
            • necrevistonnezrN Offline
              necrevistonnezrN Offline
              necrevistonnezr
              wrote on last edited by
              #28

              I managed to migrate from my current bitwarden instance (BW OLD) to the cloudron app (BW NEW) as follows:

              1. Disable 2-Factor Authentification for BW OLD (this is important!). I also removed "Organizations" in Bitwarden, I don't know if that's important, too.
              2. Open the terminal for BW OLD, go to app/data/
              3. Zip your attachments: zip -r attachments.zip attachments/
              4. Dump your existing sqlite database: sqlite3 db.sqlite3 .dump > sqlitedump.sql
              5. Drop schema creation and metadata from your dump, leaving only your actual data: grep "INSERT INTO" sqlitedump.sql | grep -v "__diesel_schema_migrations" > mysqldump.sql
              6. Still in the terminal view, hit the "Download" button (top right), enter the path to the attachments and the SQL dump (app/data/attachments.zip and app/data/mysqldump.sql) and download them.
              7. Open the terminal for BW NEW, go to app/data/.
              8. Still in the terminal view, hit the "Upload to /tmp" button (top right), upload the previously downloaded attachments.zip and mysqldump.sql
              9. Move uploaded files to data folder: mv /tmp/attachments.zip /app/data/ and mv /tmp/mysqldump.sql /app/data/
              10. Unzip your attachments: unzip attachments.zip and rm attachments.zip
                11.Import SQL Dump: mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} < mysqldump.sql (Enter like that, don't replace the variables with your username or password)
              11. Hit "Restart"

              You can now login with your Bitwarden credentials. All passwords and the attachments shoud be there.

              d19dotcaD 1 Reply Last reply
              4
              • A Offline
                A Offline
                apatheticatitude
                wrote on last edited by
                #29

                I looked into self hosting a Bitwarden instance myself a few months ago, but decided to wait for Cloudron to implement it. Excited to see it land!

                I have a couple of questions about the differences between this version and the 'standard' self-hosted one from Bitwarden itself. For one, normally the user has to provide an an installation key upon set-up which doesn't seem to be the case here.
                And it seems as though this version has access to premium and organisation features that users normally have to pay for, even while self-hosting.

                How does this implementation get around these? Is it possible the instance will break eventually or slowly fork away from the official Bitwarden server?

                d19dotcaD 1 Reply Last reply
                2
                • A apatheticatitude

                  I looked into self hosting a Bitwarden instance myself a few months ago, but decided to wait for Cloudron to implement it. Excited to see it land!

                  I have a couple of questions about the differences between this version and the 'standard' self-hosted one from Bitwarden itself. For one, normally the user has to provide an an installation key upon set-up which doesn't seem to be the case here.
                  And it seems as though this version has access to premium and organisation features that users normally have to pay for, even while self-hosting.

                  How does this implementation get around these? Is it possible the instance will break eventually or slowly fork away from the official Bitwarden server?

                  d19dotcaD Offline
                  d19dotcaD Offline
                  d19dotca
                  wrote on last edited by
                  #30

                  @apatheticatitude This already is a fork away from the official Bitwarden app. Bitwarden_RS is a fork of Bitwarden, written in Rust and allows for the premium features by simply removing parts of the code that would otherwise require a key / license. Any app that’s fully open source, one can technically remove any requirements to pay for it through modification to the code.

                  --
                  Dustin Dauncey
                  www.d19.ca

                  fbartelsF 1 Reply Last reply
                  0
                  • necrevistonnezrN necrevistonnezr

                    I managed to migrate from my current bitwarden instance (BW OLD) to the cloudron app (BW NEW) as follows:

                    1. Disable 2-Factor Authentification for BW OLD (this is important!). I also removed "Organizations" in Bitwarden, I don't know if that's important, too.
                    2. Open the terminal for BW OLD, go to app/data/
                    3. Zip your attachments: zip -r attachments.zip attachments/
                    4. Dump your existing sqlite database: sqlite3 db.sqlite3 .dump > sqlitedump.sql
                    5. Drop schema creation and metadata from your dump, leaving only your actual data: grep "INSERT INTO" sqlitedump.sql | grep -v "__diesel_schema_migrations" > mysqldump.sql
                    6. Still in the terminal view, hit the "Download" button (top right), enter the path to the attachments and the SQL dump (app/data/attachments.zip and app/data/mysqldump.sql) and download them.
                    7. Open the terminal for BW NEW, go to app/data/.
                    8. Still in the terminal view, hit the "Upload to /tmp" button (top right), upload the previously downloaded attachments.zip and mysqldump.sql
                    9. Move uploaded files to data folder: mv /tmp/attachments.zip /app/data/ and mv /tmp/mysqldump.sql /app/data/
                    10. Unzip your attachments: unzip attachments.zip and rm attachments.zip
                      11.Import SQL Dump: mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} < mysqldump.sql (Enter like that, don't replace the variables with your username or password)
                    11. Hit "Restart"

                    You can now login with your Bitwarden credentials. All passwords and the attachments shoud be there.

                    d19dotcaD Offline
                    d19dotcaD Offline
                    d19dotca
                    wrote on last edited by
                    #31

                    @necrevistonnezr That’s fantastic! Very detailed. Glad you were able to make that work. 👍

                    --
                    Dustin Dauncey
                    www.d19.ca

                    1 Reply Last reply
                    0
                    • d19dotcaD d19dotca

                      @apatheticatitude This already is a fork away from the official Bitwarden app. Bitwarden_RS is a fork of Bitwarden, written in Rust and allows for the premium features by simply removing parts of the code that would otherwise require a key / license. Any app that’s fully open source, one can technically remove any requirements to pay for it through modification to the code.

                      fbartelsF Offline
                      fbartelsF Offline
                      fbartels
                      App Dev
                      wrote on last edited by fbartels
                      #32

                      @d19dotca said in Bitwarden_rs:

                      This already is a fork away from the official Bitwarden app

                      That is not quite right. A fork implies that at some point in time bitwarden_rs and the official server shared the same code, but have diverged since then. (And at at least one side won't include that changes of the other)

                      Bitwarden_rs is an implementation of a backend component that exposes the exact same API towards the frontend.

                      Some parts that require payment in the official server have been made available in _rs anyways. Other less heavily used parts are even missing.

                      @apatheticatitude said in Bitwarden_rs:

                      Is it possible the instance will break eventually

                      Possibly. All it takes is larger or unexpected change in the API. So far the bitwarden developer has been friendly towards third party implementations however.

                      d19dotcaD 1 Reply Last reply
                      0
                      • fbartelsF fbartels

                        @d19dotca said in Bitwarden_rs:

                        This already is a fork away from the official Bitwarden app

                        That is not quite right. A fork implies that at some point in time bitwarden_rs and the official server shared the same code, but have diverged since then. (And at at least one side won't include that changes of the other)

                        Bitwarden_rs is an implementation of a backend component that exposes the exact same API towards the frontend.

                        Some parts that require payment in the official server have been made available in _rs anyways. Other less heavily used parts are even missing.

                        @apatheticatitude said in Bitwarden_rs:

                        Is it possible the instance will break eventually

                        Possibly. All it takes is larger or unexpected change in the API. So far the bitwarden developer has been friendly towards third party implementations however.

                        d19dotcaD Offline
                        d19dotcaD Offline
                        d19dotca
                        wrote on last edited by d19dotca
                        #33

                        @fbartels Ah yes, I guess technically "fork" wasn't really the right word there. The point I was trying to make is the same though... the source we are using for this app in Cloudron is already not the original/official Bitwarden server project to begin with.

                        --
                        Dustin Dauncey
                        www.d19.ca

                        girishG 1 Reply Last reply
                        0
                        • d19dotcaD d19dotca

                          @fbartels Ah yes, I guess technically "fork" wasn't really the right word there. The point I was trying to make is the same though... the source we are using for this app in Cloudron is already not the original/official Bitwarden server project to begin with.

                          girishG Offline
                          girishG Offline
                          girish
                          Staff
                          wrote on last edited by
                          #34

                          @d19dotca Yeah, I actually want to make the unofficial part a bit more clearer in our app description or maybe even our post install that Bitwarden. Also want to make sure that if paid features are being used, people take up a subscription with the upstream author. My understanding is that the main project is also a small indie company.

                          1 Reply Last reply
                          1
                          • yusfY Offline
                            yusfY Offline
                            yusf
                            wrote on last edited by
                            #35

                            I take it that the mobile apps are incompatible with the former premium features in bitwarden_rs?

                            d19dotcaD 1 Reply Last reply
                            0
                            • yusfY yusf

                              I take it that the mobile apps are incompatible with the former premium features in bitwarden_rs?

                              d19dotcaD Offline
                              d19dotcaD Offline
                              d19dotca
                              wrote on last edited by
                              #36

                              @yusf I guess it depends on what features you're referring to. Bitwarden_rs and the official Bitwarden clients (mobile apps, browser extensions, etc.) all support TOTP token storage and file storage, for example, which are both considered premium features (the $10/year if using official vault.bitwarden.com account). Any particular feature you're referring to?

                              --
                              Dustin Dauncey
                              www.d19.ca

                              yusfY 1 Reply Last reply
                              1
                              • d19dotcaD d19dotca

                                @yusf I guess it depends on what features you're referring to. Bitwarden_rs and the official Bitwarden clients (mobile apps, browser extensions, etc.) all support TOTP token storage and file storage, for example, which are both considered premium features (the $10/year if using official vault.bitwarden.com account). Any particular feature you're referring to?

                                yusfY Offline
                                yusfY Offline
                                yusf
                                wrote on last edited by yusf
                                #37

                                @d19dotca Organisations, on the iOS client.

                                Would it work to first sign up for premium on their hosted service, somehow unlocking the app, then switch that to self-hosted?

                                d19dotcaD 1 Reply Last reply
                                0
                                • yusfY yusf

                                  @d19dotca Organisations, on the iOS client.

                                  Would it work to first sign up for premium on their hosted service, somehow unlocking the app, then switch that to self-hosted?

                                  d19dotcaD Offline
                                  d19dotcaD Offline
                                  d19dotca
                                  wrote on last edited by d19dotca
                                  #38

                                  @yusf It works with organization in the sense that items shared in an organization will show up and you can add new items to an existing organization. One limitation though in the mobile app is that you can’t create an organization, you have to do that in the web app. That’s a general Bitwarden limitation though, not Bitwarden_rs specifically.

                                  Screenshot below shows the test item I created in a test org, and has a share icon next to it to signify its from a shared organization.

                                  A4BA27E9-8EDF-4058-8BE4-64BF738E4F0D.jpeg

                                  Screenshot below shows how to assign to an org. The org I have is called test. The scribbled out option is the personal account. Test is the org.

                                  AD14466D-E03F-4222-B996-EE2372D0F224.jpeg

                                  --
                                  Dustin Dauncey
                                  www.d19.ca

                                  1 Reply Last reply
                                  0
                                  • yusfY Offline
                                    yusfY Offline
                                    yusf
                                    wrote on last edited by
                                    #39

                                    @d19dotca Oh, I see. I was looking for the organization as a folder, not as items. Good news.

                                    1 Reply Last reply
                                    0
                                    • necrevistonnezrN Offline
                                      necrevistonnezrN Offline
                                      necrevistonnezr
                                      wrote on last edited by
                                      #40

                                      If a user signs up on my bitwarden instance, the email invite is not sent. Neither if I add a user to an organisation.

                                      config.env looks like this:

                                      # Export bitwarden rs environment variables here to ovveride the defaults
                                      export SIGNUPS_ALLOWED=true
                                      export INVITATIONS_ALLOWED=true
                                      # To only allow users with the same email domain as where the app is installed:
                                      # export SIGNUPS_DOMAINS_WHITELIST=ckfl.net
                                      #export LOG_LEVEL=debug
                                      

                                      Or is there a way to manually approve a user?

                                      1 Reply Last reply
                                      0
                                      • doodlemania2D Offline
                                        doodlemania2D Offline
                                        doodlemania2
                                        App Dev
                                        wrote on last edited by
                                        #41

                                        That should be working. Check your outbound mail settings and logs to see if it is stuck somewhere?

                                        1 Reply Last reply
                                        1
                                        • necrevistonnezrN Offline
                                          necrevistonnezrN Offline
                                          necrevistonnezr
                                          wrote on last edited by
                                          #42

                                          Indeed, the mail - relayed via sendgrid - was blocked by the recipient email provider mailbox.org:

                                          554 5.7.1 Service unavailable; Client host [167.89.24.164] blocked by RBL; Blocked - see https://www.spamcop.net/bl.shtml?167.89.24.
                                          
                                          1 Reply Last reply
                                          0
                                          • doodlemania2D Offline
                                            doodlemania2D Offline
                                            doodlemania2
                                            App Dev
                                            wrote on last edited by
                                            #43

                                            Strange that sendgrid got RBLed...but that's going to be something they will need to straighten out.

                                            necrevistonnezrN 1 Reply Last reply
                                            0
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes


                                              • Login

                                              • Don't have an account? Register

                                              • Login or register to search.
                                              • First post
                                                Last post
                                              0
                                              • Categories
                                              • Recent
                                              • Tags
                                              • Popular
                                              • Bookmarks
                                              • Search