[Bug]: Migration failed

[borisrorsvort]

Real Outcome

At this point it’s not good, as we dont know what to do anymore. When rewriting from scratch is ever a good idea? Plugin was working well for me before...

What should I do now?

Expected Outcome

Have comprehensive error and steps to follow

Backend

Webdav via tailscale

Steps to Reproduce

Proceed with migration

Support Log

son","package.json","test.md","✱ Home.md"]`
- 2026-08-08 12:10:30 **INFO** Planning finished with 0 tasks
- 2026-08-08 12:10:30 **INFO** Execution started
- 2026-08-08 12:10:30 **INFO** Sync completed with no changes — `{"progressSummary":{"completed":[],"completedTasks":0,"totalTasks":0},"remoteWalkSummary":{"completedItems":170,"currentItem":"/Obsidian/Home.md","totalItems":170},"resultSummary":{"failed":[],"failedTasks":0,"succeededTasks":0,"totalTasks":0},"timestamps":{"queuedAt":1786183827008,"updatedAt":1786183830912,"planningStartedAt":1786183827008,"endedAt":1786183830912,"durationMs":3904}}`

Issue Policies

• I agree to follow this project's issue policies and confirm:

[hesprs]

I feel very sorry about the disturbance. Don't worry if the migration fails, WebDAV Sync will still function normally.

If you think upgrading to Sync Engine is unnecessary, you can click Never show again when next time the migration window pops up. WebDAV Sync will work forever. If you would like to give Sync Engine a try, you can read this page in documentation and perform a manual migration.

[hesprs]

Please wait, if you want a smoother migration experience. I can provide you a patched version of WebDAV Sync.

[hesprs]

Migration routine patched. If you want to continue the migration, download https://github.com/hesprs/sync-engine/releases/download/2.5.14/main.js, replace <your-vault>/.obsidian/plugins/webdav-sync/main.js, and try migration again.

Apologize again for the disturbance.

[terminar]

@hesprs Same problem here.

First of all, thank you for your work, "WebDAV Sync" was a helpful alternative to "remotely save" (doesn't work anymore here).
But I had some problems (sync often just "hang" when getting different files and file listing remotely, ...). Another obsidian repository just isn't working (around 60gb of files). But still - WebDAV Sync was the best alternative for me and I really loved the approach.

Now some feedback for the "sync engine" stuff.... As a developer I can understand that a "restart" or "version2" or whatever does really makes sense. But as a user I had some problems.

• I had version 2.5.11 installed on my Mac without auto update, on my iPhone there was the auto updater active. The updater told me that there is sync engine now and so on but I didn't want to do that on my phone. On my Mac that popup for migration didn't occur due to the older version. I searched for 2.5.12 or 2.5.13 but every time I was redirected to sync engine (and there is nothing mentioned on the GitHub README.md about "yes, that's WebDAV Sync, old version available at ". I just realized, ok, the older version is just somewhere in the releases, I have to manually download it, replace the files, whatever. I think some information about the old version would help users to jump over.

• the manual approach mentioned at https://sync.consensia.cc/usage/migration says at "Manual Migration/6.":
  Go to your WebDAv Backend and delete the remote root. Perform a fresh sync on one of your devices to upload your files, delete all files on your other devices." => which means (if I understand correctly) I have to select one device which should act as new central of trust, remove every synced file on other devices and my backend and re-sync EVERYTHING again? I hope that is not what you intended (because even this was not needed with WebDAV Sync). Can you please clarify the situation?

Regarding the fixed 2.5.14: I don't get the net:ERR_INSUFFICIENT_RESOURCES anymore but "Migration failed: 503: you are not allowed to connect, The migration is reverted, nothing is destroyed".

Erm, what? Destroyed? Can you give some more insight what happens here, if there will be a completely new sync or if it's more secure to leave the data and both plugins (WebDAV Sync and sync engine) until there is some stability?

Sorry if this maybe sound rude (it doesn't mean to) but I am really afraid of loosing data (or even completely resync my whole stuff across all of my devices).

[hesprs]

@terminar Very sorry for the disturbance and confusion, I will update the README and documentation immediately with more detail.

There's nothing to fear here. Both WebDAV Sync and Sync Engine are stable. The only real issue you met is the migration failure, and that doesn't make you lose any data. "Nothing is destroyed" means the migration routine is read-write only, it doesn't delete anything. And upon sync failure, it only deletes what it has written.

The documented manual migration steps are really confusing, I will update them immediately.

What you can do now:

• If you want comfort right now, go to all your devices, when the migration notice appears, click "Never show again". Then everything will back to normal. WebDAV Sync is designed to be still function when user denies the migration.
• If you want to migrate manually and give a try to Sync Engine. You DO NOT need to re-sync your vaults. That's a documentation failure. You should (1) Deny WebDAV migration notice. (2) Launch syncs as normal in WebDAV Sync to ensure every file is aligned on all devices. (3) Uninstall WebDAV Sync. (4) Install Sync Engine. (5) Go to its settings, download the WebDAV module in module management panel, configure your accounts, and disable the "Asymmetric storage" setting. (6) Ensure step 5 is performed on all devices and you DO NOT need to delete any data. (7) Launch a sync in Sync Engine, if all data on your devices and remote is aligned, it should pick up your state, only populates its internal record, and shows "Already synced".

[hesprs]

Now README and migration documentation are both updated for minimal confusion.

[borisrorsvort]

@hesprs

Weddav module loaded, exact same url, credentials and path as previously and the SSH connection is failing.
Reverting to webdav works fine.

Generated at: 2026-08-09 14:01:26
Plugin version: 3.0.3
Obsidian API version: 1.13.4
Operating system: macOS

Trigger: manual
Started at: 2026-08-09 14:01:16
Ended at: 2026-08-09 14:01:16
Duration: 77 ms
Outcome: failed
Logs:

INFO - Sync triggered by manual started.
ERROR - Sync ended with error: net::ERR_SSL_PROTOCOL_ERROR.
General logs:

14:00:14 - INFO - Module smart-merge loaded.
14:00:14 - INFO - Module webdav loaded.
14:00:14 - INFO - Discovered 7 module(s) from 1 source(s).

[terminar]

@hesprs Documentation is much better, thank you.

When I try to proceed with the automatic migration via "Proceed" with 2.5.14 it takes around one minute and I receive:

Migration failed

Migration failed: 503: you are not allowed to connect

The migration is reverted, nothing is destroyed.

Accepting this with "Close" and immediately doing a manual sync with WebDAV Sync 2.5.14 is working as expected when I do a standard sync (so settings seem to be OK), I don't get 503 or any error.

[hesprs]

@borisrorsvort After digging in the code I cannot find any evidence why the SSL succeeds in WebDAV Sync but fails in Sync Engine. Are you using any proxy? Or you mistakenly spelled http to https or https to http? This is usually hard to find at first glance.

[hesprs]

@terminar Could you please try setting "Max concurrent WebDAV requests" in WebDAV Sync setting to a lower number, for example 8, and try migration again?