Updated July 2026 · 6 min read
Sync settings with WebDAV
WebDAV backup asks for only three things: a server address, a username and a password. All the difficulty sits in how deep the address goes and which password the service actually wants.
What goes in the three fields
The server address is the WebDAV address your storage provider publishes, and the username is usually a full email address or account name. The password field is where things go wrong, because many services reject the password you log in with.
What they want is an app password or authorisation code generated separately in the security settings, and accounts with two-factor authentication accept nothing else. It is typically shown once, so copy it there and then; self-hosted Nextcloud and similar servers work the same way.
How deep the address should point
The WebDAV address often lives on a different host or path from the web interface, so take that line from the provider documentation rather than copying whatever your browser address bar shows.
Point the address at the folder that will hold the backups, and create that folder in the storage first — the client will not build a nested path for you. The trailing slash matters too: some servers accept it either way, others return 404 without it, so add one when a connection refuses to work. Use https, not http.
A wrong address usually shows up as a connection that succeeds and then cannot find the path. Make sure you entered the WebDAV address from the provider documentation, not the web interface link from your browser.
Reading a failed connection
An authentication error means the address and the network are fine and only the identity was rejected — nine times out of ten the password field holds a login password, or the username is missing its domain part. Try the app password instead.
A missing path or not-found error means the folder does not exist or the address dropped a segment; a method-not-allowed response means the address is not a WebDAV endpoint. One case is easy to miss: with TUN or the system proxy on, the client sends its own requests through the proxy, so a broken proxy path takes the upload with it.
It is not live synchronisation
Sync here means one upload per click; editing a subscription pushes nothing on its own, and restoring means picking an archive and pulling it back by hand. Upload once before switching machines rather than assuming the copy in the cloud is current.
Two machines writing into the same folder overwrite each other, the last upload wins, and nothing is merged for you. Give each machine its own subfolder, or agree that only the main machine uploads and the other one only restores.
What is the project?
Clash Verge Rev is a Tauri-based GUI for Mihomo with profile management, system proxy, TUN mode, rule editing and WebDAV backups.