vrtmrz
0.24.18 - sync stopped working
With the recent update - sync stopped working at all. Could not connect to server on all devices.
when updating to latest version - setting doctor pops up and proposes to modify Compute revisions for chunks (Previous behaviour). When You do that sync stop working unless You explicitly press "Replicate now" and change server setting. Then You have to modify parameter on every device. It is not straight forward and could be good mo modify both local and remote setting with "doctor" feature.
Also ran into this issue. The wizard says the value true is recommended so I apply it, but it does not tell me to trigger a replication just that I need to change the value on all devices (which I did and then I was confused that it didn't sync anymore).
After triggering the replication on my 'main' device, the other device says:
01/03/2025, 22:18:08->The remote database has been rebuilt or corrupted since we have synchronized last time. Fetch rebuilt DB, explicit unlocking or chunk clean-up is required.
But none of these options exist in the menu...
Edit: it looks like the option is 'Replicate now' and then you press 'Fetch all from the remote database again' and then 'Yes' to create local chunks and speed up the process. For me it took a while. It will also pop up if you want to enable extra features which I press 'No' because the settings sync completely exploded last time 😢 Might be good to update this message to include explicit instructions of running 'Replicate now' and 'Fetch all from remote'
After the sync you have to also manually toggle livesync to actually start the synchronization process. On two devices I got an icon of a phone flickering for a few minutes, but eventually it disappeared.
On one device I got a replication error, but I disabled sync, restarted and enabled sync and it was also fixed 🤷♂
I had a similar issue when setting up CouchDB again a few months ago and it was related to permissions/CORS settings which moved to a different location. Unfortunately I didn’t take notes, but I think going over the guide again step by step to make sure those CORS settings are set will fix it.
I had a similar issue when setting up CouchDB again a few months ago and it was related to permissions/CORS settings which moved to a different location. Unfortunately I didn’t take notes, but I think going over the guide again step by step to make sure those CORS settings are set will fix it.
Thanks, I checked the settings. CORS is enabled and even if I allow origins *, the behavior is still the same.
I ran into the same problem too! Turning on the Patches ---> Compatibility (Trouble addressed) ---> Do not check configuration mismatch before replication option did the trick for me, though I’m not totally sure if it might mess something else up down the line.
Sorry for being absent! Possibly, some devices have unmatched configurations.
The Doctor prompts to correct sub-optimal settings. This is for configurations of the device which doctor had been run. On the other hand, the configuration mismatch check before replication warns that the settings of the connected devices do not match. If the settings have been changed in Doctor, this may, of course, result in a warning. If this is the case, you will need to change the settings stored in the database to which you are connected, by using the settings for this device (otherwise, this will be repeated many times if the remote settings are imported).
Admittedly, this is a confusing area and we would like to do something about it.
However, if configuration mismatch have been detected as , this means that there are potentially problem and replication will be prevented. It is recommended to re-apply the configuration if possible, instead of disabling this feature.
(If you find it confusing to do this in that dialogue, you can of course do it using the Set-up URI, or by the QR configuration transfer implemented in v0.24.19).
Would you mind if I ask you to check the behaviour after matching configuration, please?
If the settings have been changed in Doctor, this may, of course, result in a warning. If this is the case, you will need to change the settings stored in the database to which you are connected, by using the settings for this device
@vrtmrz May I ask how to change the settings stored in the database? We have the "Fetch config from remote server" button, but there is no "Push local config to remote server."
Is rebuilding DB the only option?
