You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a KeePass 2 database that is stored on NextCloud and is accessed with KeePassXC on my MacBook. Using the NextCloud app KeeWeb (v1.8.2), I created a new record in the database. Now KeePassXC is unable to open the file, displaying the following in red when the password and key file are provided:
Error while reading the database: Invalid number value
Although KeePassXC cannot open the database, MacPass (v0.7.9) and Strongbox (v1.11.0) both open it without issue. I can also open the kdbx file with KeeWeb on NextCloud.
After testing, this happens every time a new record is created in the NextCloud app KeeWeb (v1.8.2), although it's not the new record that's the issue. I can open the kdbx file with MacPass and delete the new record, but KeePassXC will still not open the file and reports the same error (invalid number value).
I have a KeePass 2 database that is stored on NextCloud and is accessed with KeePassXC on my MacBook. Using the NextCloud app KeeWeb (v1.8.2), I created a new record in the database. Now KeePassXC is unable to open the file, displaying the following in red when the password and key file are provided:
Error while reading the database: Invalid number value
Database format: KeePass 2
KeePass file version: 3.1
Database generator: KbdxWeb
Outer encryption: AES
Compressed: yes
Transform rounds: 600000
Inner encryption: Salsa20
Number of entries: 332
Although KeePassXC cannot open the database, MacPass (v0.7.9) and Strongbox (v1.11.0) both open it without issue. I can also open the kdbx file with KeeWeb on NextCloud.
Debug Info
KeePassXC - Version 2.4.3
Revision: 5d6ef0c
Qt 5.12.3
Debugging mode is disabled.
Operating system: macOS High Sierra (10.13)
CPU architecture: x86_64
Kernel: darwin 17.7.0
Enabled extensions:
Cryptographic libraries:
libgcrypt 1.8.4
The text was updated successfully, but these errors were encountered: