#22

Thank you for using this plugin!
But it is something mysterious.
Your vaults have been synced once, but no more sync again…

Please check the remote URI and databases are exactly the same once again?

The latest change sequence no is shown in the sync log, if you enable verbose log. update_seq is so.

#23

Have you enabled any sync?

If any sync is enabled, it could not be able to
change.

#24

Double checked the connection to the database, URI, username, password, database name and all he same. I hosted my couchdb behind the caddy, CORS sets to enabled with “*” or “app://obsidian.md,capacitor://localhost,http://localhost” still acts the same. If the CORS is set to disabled then each peer cannot connect to the database. Since the first time android app could download all the notes, I think it may not be the issue of CORS. I will try to capture network packets on the database and see if anything goes wrong.

I found two files under my couchdb docker:

  • /couchdb/data/shards/00000000-7fffffff/obsidian.1638094448.couch
  • /couchdb/data/shards/80000000-ffffffff/obsidian.1638094448.couch

Would this mean I have two vault to sync with mobile and laptop app separately?

#25

Thank you for checking your settings! And your CORS configurations are right.
Splitting shard is the normal behavior of CouchDB. It’s for clustered Databases. Do not worry about it.

Are there any warnings shown on Settings Dialog?
The warning is shown with the red border. like this:
image

These warnings are shown after being replicated once.

If any warnings are shown, please answer each warning and try to replicate again.

#26

Yes there were two warnings and I have checked both of them on each peer, one is this about incompatibly and another is about lock the database for damage.

It’s quite strange, I’ll check with the public couchdb service and see if my docker (apache/couchdb, v3.2.1) causes the issue.

#27

Never mind, it’s notified from Self-hosted LiveSync.

Sometimes, by timing problem, the plugin detects the differences caused by the migration of local databases (or false positive.)

The plugin stops replications as safely as possible.

When once detected, It won’t be shown by the next incompatible version up.

Please try resolving warnings. Sorry for the inconvenience.

#28

Yes you’re right Thanks. I supposed that the plugin supports webdav sync but I am wrong since I haven’t read your post carefully. :joy:

Never mind. Thank you for your great work.

#29

I tried with two laptops today, and they could sync up with each other, with the same server and same configurations, seems it’s only my Android mobile has the issue. I’ll try to find out why.

Two questions:

  • the “Device and Vault name”, is it just an identifier for different device or is it must be the same on different peer?
  • I see “local database” mentioned in the settings, where is the local database locates? I couldn’t find it on Windows or Android.
#30

I’m glad to hear that your PC could be synced!
Then we have to solve the Android problem.
If you set Android to “Developer mode” and enable debugging. Your device will be inspected by PC.
After connecting to pc, open “chrome://inspect/#devices” on your Chrome, you will get all verbose log messages and network errors.
Could you try this?

Answers:

  • Device and Vault name
    These are the settings for synchronizing plugins and settings. if you don’t use it, never mind. But it must be a different value between devices.
  • Loca Database:
    This is transparent for you. Please refer techical informations