AronM

The software uses the native Bitwarden CLI to create and encrypt your export. You should be able to use Bitwarden's import functionality to restore this file, please see the following URL for more information on this process: https://bitwarden.com/help/import-data/#tab-web-app-5ALQx9afSqWXX9jfXsY5sb.

I've had another look at this issue, it seems like an incorrect Stream disposal caused the JSON to not be written to disk correctly. This has been resolved in version 1.0.3. Thank you for bringing this to my attention, @stayupthetree.

If the file is created in the config directory, the permissions should have been set correctly. What happens when you either delete the appsettings.json file and let the application recreate it, or fill it manually based on the sample file?

Support for the bitwarden-secure-sync tool. Source: https://github.com/AronMarinelli/bitwarden-secure-sync Docker Hub: https://hub.docker.com/r/aronmarinelli/bitwarden-secure-sync General documentation: https://github.com/AronMarinelli/bitwarden-secure-sync/blob/main/README.md This tool enables you to export your Bitwarden vault to a local file periodically. It uses the Bitwarden CLI tool to communicate with the API, and exports your passwords using the default Bitwarden export method.