Why 404 / 405 happens
Syncing starts by checking whether a file already exists on the server. The WebDAV spec says a HEAD request answers that, but plenty of servers implement HEAD loosely — the file is there, yet the response is 404 or 405, and the sync stops.
This is a difference in protocol implementation. It does not mean you filled something in wrong, and it does not mean your data is damaged.
The compatibility handling is already on
For custom WebDAV servers, KeyMe Pass defaults to the more forgiving checks:
- No HEAD requests — existence is checked with GET instead
- Directories and large files (including attachments) are checked with PROPFIND
There is nothing to switch on, and no way to switch it off. Earlier versions offered a "standard / enhanced" choice in settings; that option has since been removed and the enhanced behaviour made unconditional. If an older guide tells you to enable it, the toggle simply is not there any more — that is expected.
If it still fails
Work through these in order:
- Is the URL the WebDAV endpoint? It is often not the same address as the service's web interface.
- Are the credentials the right ones? Several services require a separately generated app password rather than your normal sign-in password.
- Does the storage path exist? The default is
/keyme. Some servers will not create it for you — make the folder first. - Can that folder be written to? Read-only access connects fine but cannot upload.
- Does the server support PROPFIND? It is a basic WebDAV method; a few stripped-down servers disable it, and no client-side setting can work around that.
If switching to the hosted storage syncs normally, the problem is almost certainly on the self-hosted side.
Your data stays protected either way
Whichever server you use, and whether or not the sync completes, data is encrypted on your device before it is uploaded — the server only ever holds ciphertext. These errors affect whether syncing finishes, never whether content reaches the server in the clear. See the security page.