Where is all explained. There must be TWO separate databases. Your local copy that you open and update, and a "master" copy with a different name that gets updated automatically via the triggers whenever you update or open your local copy. The master copy can be on a local NAS or on any public cloud server. I actually recommend the latter as you then have a copy that is not subject to local disasters by being off-site. The database encryption ensures that the cloud copy cannot be opened without the password. I could give you a copy of my own database file and be confident you cannot open it.
The master copy can be updated via triggs from more than one device and changes get merged each time the master copy is merged with the local copy. More recent entries take precedence but the previous version of every entry is stored in the entry history so no data is ever lost.
You can then share the cloud copy with other devices which do not need to be in your location. I use an Android port so it is on my phone. It does still need the password to be entered to open it.
I hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sync is always manual (unless you use triggers) and if you have made a change you need to sync again.
You can save and then sync or just sync, as sync is also a save.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any thoughts about switching to a public cloud service for your Keepass master data file to give you the protection of offsite backup rather than a NAS as I suggested? The Keepass database encryption makes this safe and it is far more disaster proof than a local NAS.
For historical reasons I actually use TeamDrive (Synqion in the USA for complicated legal reasons) which is an encrypted cloud service that can be safely shared via a shared folder but accessed by any local programs (it is strongly encrypted on the cloud file storage) but I would be perfectly happy with using Google or Microsoft cloud services. KeePass does not need the additional encryption but oher giles I share do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know, but I don't want to use Big Tech cloud services. Of course the NAS-copy is not the only one and I have seen that I could integrate backup as a trigger too.
But actually more urgent, I'll have to find solutions for
using Keepass (with browser integration) ) on my Android devices
integrate Keepass in my desktop-browsers (Firefox / Vivaldi / Opera)
and find a desktop solution for an entry-view in which the fields are clickable (--> copy to clipboard / launch program a.s.o.). Actually I'm using KPEnhancedEntryView.plgx but to copy something still a right-click is needed . I also had a look at KeePassXC, but that one misses many other mandatory features.
Last edit: darwin4ever 2025-12-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
If have a synchronising problem with my Keepass2 2.60 x64 (Windows)
I created a copy of my database MyDatabase.kdbx pn my NAS-device as MyDatabaseCopy.kdbx and did a manual "Synchronise with File". That works.
But when I change/save an Entry and/or Exit Keepass, the sync doesn't work, Nothing is copied to the copy on the NAS.
What am I overlooking ? I searched the settings but couldn't find anything related to Synchronising
You would appear to have not yet found the description of "Triggers" https://keepass.info/help/v2/triggers.html#examples and https://keepass.info/help/kb/trigger_examples.html
Where is all explained. There must be TWO separate databases. Your local copy that you open and update, and a "master" copy with a different name that gets updated automatically via the triggers whenever you update or open your local copy. The master copy can be on a local NAS or on any public cloud server. I actually recommend the latter as you then have a copy that is not subject to local disasters by being off-site. The database encryption ensures that the cloud copy cannot be opened without the password. I could give you a copy of my own database file and be confident you cannot open it.
The master copy can be updated via triggs from more than one device and changes get merged each time the master copy is merged with the local copy. More recent entries take precedence but the previous version of every entry is stored in the entry history so no data is ever lost.
You can then share the cloud copy with other devices which do not need to be in your location. I use an Android port so it is on my phone. It does still need the password to be entered to open it.
I hope this helps.
Sync is always manual (unless you use triggers) and if you have made a change you need to sync again.
You can save and then sync or just sync, as sync is also a save.
cheers, Paul
Thanks !
It's working now, I had no clue that triggers are needed for syncing to be active
That is good news!
Any thoughts about switching to a public cloud service for your Keepass master data file to give you the protection of offsite backup rather than a NAS as I suggested? The Keepass database encryption makes this safe and it is far more disaster proof than a local NAS.
For historical reasons I actually use TeamDrive (Synqion in the USA for complicated legal reasons) which is an encrypted cloud service that can be safely shared via a shared folder but accessed by any local programs (it is strongly encrypted on the cloud file storage) but I would be perfectly happy with using Google or Microsoft cloud services. KeePass does not need the additional encryption but oher giles I share do.
I know, but I don't want to use Big Tech cloud services. Of course the NAS-copy is not the only one and I have seen that I could integrate backup as a trigger too.
But actually more urgent, I'll have to find solutions for
Last edit: darwin4ever 2025-12-31
cheers, Paul