Configuration mismatch warning at startup despite synchronized versions and configurations​

[dosoft]

Upon starting Obsidian with the LiveSync plugin enabled, I receive the following warning message: "Configuration mismatching between the clients." This occurs even though I have ensured that all my clients are running the same version of both Obsidian and the LiveSync plugin, and their configurations appear to be identical.​

I am seeking guidance on how to identify the specific configuration discrepancies causing this warning and how to resolve them.​

[Tigo72]

I second this issue and call for guidance. I cannot Validate Database Configuration either. Error message: checking configuration failed.

[przemhb]

The same happened to my 4 clients. Furthermore, they ceased to sync with each other.

[vrtmrz]

Sorry for being long absent!

In design, the mismatched configuration is displayed as a dialogue, allowing the user to select the configuration to be used from those stored on the device or remotely. Does this mean that the dialogue does not appear?

To check that the settings really match, Please make reports on each device by Prepare the report to create an issue on the Hatch pane of the settings, and compare them. Of course, I also will address it if you share it with the issue!

[dosoft]

In design, the mismatched configuration is displayed as a dialogue, allowing the user to select the configuration to be used from those stored on the device or remotely. Does this mean that the dialogue does not appear?

I only see this popup, which disappears after a few seconds. No additional dialog appears.

[przemhb]

In case of every client, "doctor" pop-up appeared suggesting fixing the settings. In each case, I have chosen the recommended settings. Later I will gather settings from all those clients and compare them.

[przemhb]

Differences in configurations among my 4 clients:

Navigator: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/1.8.4 Chrome/130.0.6723.191 Electron/33.3.2 Safari/537.36
FileSystem: insensitive
showVerboseLog: false
resolveConflictsByNewerFile: false
deviceAndVaultName: neutrino
additionalSuffixOfDatabaseName: f21c48b9f4f734d1
notifyThresholdOfRemoteStorageSize: 1503
useAdvancedMode: true
usePowerUserMode: true

Navigator: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/1.6.7 Chrome/124.0.6367.243 Electron/30.1.2 Safari/537.36
FileSystem: insensitive
showVerboseLog: true
resolveConflictsByNewerFile: false
deviceAndVaultName: laptop-praca
additionalSuffixOfDatabaseName: 4814a470abd08344
notifyThresholdOfRemoteStorageSize: 1554
useAdvancedMode: true
usePowerUserMode: false

Navigator: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/1.8.9 Chrome/132.0.6834.210 Electron/34.3.0 Safari/537.36
FileSystem: insensitive
showVerboseLog: false
resolveConflictsByNewerFile: false
deviceAndVaultName: laptop
syncInternalFilesIgnorePatterns: \/node_modules\/, \/\.git\/, \/obsidian-livesync\/
additionalSuffixOfDatabaseName: c955db86fd5bd604
notifyThresholdOfRemoteStorageSize: 1553
usePowerUserMode: false

Navigator: Mozilla/5.0 (Linux; Android 13; LM-V600 Build/TKQ1.220829.002; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/134.0.6998.39 Mobile Safari/537.36
FileSystem: sensitive
resolveConflictsByNewerFile: true
deviceAndVaultName: Telefon-LG-V60
additionalSuffixOfDatabaseName: /storage/D7AF-3330/Notatniki/Obsidian-Vault/Notatniki
notifyThresholdOfRemoteStorageSize: 2000
useAdvancedMode: false
usePowerUserMode: false

Could they lead to the message and render sync not working?

[ZeroEkkusu]

Here's how I fixed it:

Open the command palette and run "Replicate now".

A window with a warning will appear.

Select the option to update the "remote" configuration (no need to rebuild, etc.).

That's it.

[przemhb]

@ZeroEkkusu Thank you. It helped.
(It shouldn't happen in the first place.)

[rawGH]

Does not help me. Updated to 24.23, I've tried every type of reset, short of doing it all by hand from scratch or total overhaul. Sync never works from PC or Android phone. When refetching from server DB it seems to work for the first time, but settings are acting weird - you can't run Test Database connection, just nothing happens, no error either, although it works when fetching data from scratch. Remote type (db) is sometimes grayed out, but other times you can choose between options. I've copied the settings multiple times, reset, rebuild... I don't want to set up DB and clients everytime theres an update, this is becoming a reoccuring thing for me (third time already), and I don't use any specific settings that could be the problem. Generic, common install with live sync enabled. I love your plugin, it's hard to live without it, but I've been at this for 2h now and if I manage to fix it, I'll never update again.

[vrtmrz]

So sorry for your trouble!

Remote type (db) is sometimes grayed out, but other times you can choose between options.

These entries cannot be changed during any synchronisation has been enabled. Please apply the preset Disable all automatic to disable it.

It is possible that some settings are not detected properly. I wish I had been allowed to check the reports for all devices, but it seems to keep bothering you. I am really sorry. If you run Doctor and it still does not detect it well, you can toggle on Patches -> Do not check configuration mismatch before replication in the setting dialogue to be free from it. (If Patches is not there, please toggle Setup -> Enable edge case treatment features first). And, if I change the behaviour significantly, next time I would raise the minor version (b in a.b.c), even if I think the compatibility is maintained.

I hope that the trouble can be avoided by using the Edge Case Treatment. Please check it once.

Note: Just for information, to be documented. But seems something is wrong...

• Configuration Mismatch detection entries are the following:

  • "minimumChunkSize"
  • "longLineThreshold"
  • "encrypt"
  • "usePathObfuscation"
  • "enableCompression"
  • "useEden"
  • "customChunkSize"
  • "useDynamicIterationCount"
  • "hashAlg"
  • "enableChunkSplitterV2"
  • "maxChunksInEden"
  • "maxTotalLengthInEden"
  • "maxAgeInEden"
  • "usePluginSyncV2"
  • "handleFilenameCaseSensitive"
  • "doNotUseFixedRevisionForChunks"
  • "useSegmenter"

• Doctor checking entries are the following:

  • "sendChunksBulk": should be false
  • "sendChunksBulkMaxSize": must be 1
  • "doNotUseFixedRevisionForChunks": should be true
  • "handleFilenameCaseSensitive" should be false (and requires rebuild)
  • "useIndexedDBAdapter": Recommended to be true (and requires rebuild)
  • "useEden": Recommended to be false.
  • "hashAlg": Not be sha1 and xxhash32
  • "disableCheckingConfigMismatch": should be false (this problem).
  • "enableCompression": should be false

[rawGH]

Don't worry about it. I was just frustrated with it. Somehow managed to get the PC version working by resetting everything and re-do all the settings manually (luckily I had everything documented from last update). Then I tested it on a completely new android phone; tried to copy settings from PC, but when I tried copy/paste the full URL app said it was unrecognized. When I tried QR code, it worked and settings were copied. Then the same problem happened where it just would not sync. Tested a couple of things, doctor said no errors, but test db did nothing... then I reset everything, entered manually and now it works. There might be some minor bug with the settings that were nagging me, or I might be doing something wrong, in any case not touching it now.

I love the plugin, I love the idea, I can also appriciate all the work and many options, but maybe build a basic-super-stable version separately and not touch it ever(ish). Just an idea.

[koteitan]

In my case, updating from 0.24.11 to 0.24.25 triggered a configuration mismatch warning. Enabling Remote Configuration → Fetch Settings → Fetch → Use remote configuration resolved the issue, although I'm not sure if this is the correct or intended fix.

I can reproduce the same warning using Doctor: open Doctor, then it said "Configuration name: Compute revisions for chunks (Previous behaviour), Current value: false, Ideal value: true", click Fix it, and the configuration mismatch warning appears again.

[zzahkaboom24]

In my case, updating from 0.24.11 to 0.24.25 triggered a configuration mismatch warning. Enabling Remote Configuration → Fetch Settings → Fetch → Use remote configuration resolved the issue, although I'm not sure if this is the correct or intended fix.

I can reproduce the same warning using Doctor: open Doctor, then it said "Configuration name: Compute revisions for chunks (Previous behaviour), Current value: false, Ideal value: true", click Fix it, and the configuration mismatch warning appears again.

Doctor -> "Configuration name: Compute revisions for chunks (Previous behaviour)" gave me the same configuration mismatch issue, however @ZeroEkkusu's fix on doing CTRL + P -> Self-hosted LiveSync: Replicate now -> Update remote database settings but keep as is was what worked for me. After clicking Update remote database settings but keep as is, seemingly nothing happened, but it was only a matter of waiting for a few minutes until it actually started replicating. After that it finished quickly.

[zigmasdirigeant]

Here's how I fixed it:

Open the command palette and run "Replicate now".

A window with a warning will appear.

Select the option to update the "remote" configuration (no need to rebuild, etc.).

That's it.

This helped. As an extra, if you have sync in multiple devices, do the same in all the devices. When syncing all of them, close the app on all of them, open again in all of them, and replicate in all of them. That should make the message stop.