vorotamoroz

Thank you for the detailed information! Did you roll LiveSync back? `Check remote configuration` looks like it had not test `chttpd.max_http_request_size` and `couchdb.max_document_size`. These items are only on 0.14.3 or...

Thank you for your careful verification! It getting be clear! I appreciate that you did not gave it up. May be, the chunk that h:+480891820 is too large to configuration....

@justemu It should have been fixed at 0.15.9. Could you please try?

Some of you have already noticed and contributed, but let me announce it. Now Self-hosted LiveSync has an i18n feature. We can add new translations by following the document. [Adding...

Thank you for notifying this issue! This may caused by `Fetch chunks on demand`. This feature requires serverside work. When we enable this feature, we synchronise only notes and then...

Thank you for the detail! This suggests that Self-hosted LiveSync missed the `checkpoint` and had traced the changes from the beginning of the remote database (Only read and check, no...

@JamborJan Thank you for updating the plug-in! Looking at the information you provided, the synchronisation indicates it has balanced, as you have pointed out. The next possibility might be a...

Thank you for your try! If no mismatch has been found on every (it is possible that if a device has the latest file, it is not reflected in the...

Sorry for being late! And, am also sorry for the misdirected guidance. In retrospect, it seems that I did not have a deep understanding of what caused the situation. At...

Sorry for being late! It seems that the CouchDB was force-terminated by an Out-of-memory killer. `Fetch chunks on demand` act in two phases. 1. Synchronise only notes using design documents...