Document rclone limits on Nextcloud file-drop shares.
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s

File-drop WebDAV allows PUT/MKCOL/MOVE only; listing and rclone copyto
metadata checks fail with 405. Backup uploads stay on curl PUT.
This commit is contained in:
tegwick 2026-07-07 19:54:43 +02:00
parent d238d5ccc7
commit 49c2180a99

View file

@ -61,8 +61,36 @@ Using `/public.php/webdav/` returns HTTP **409** (*Files cannot be created in
non-existent collections*) on current Nextcloud — that path is not valid for
public file-drop shares.
Uploads use a direct HTTP PUT via curl (`-u <token>:`). rclone is optional;
the backup scripts do not require it.
Uploads use a direct HTTP PUT via curl (`-u <token>:`). The backup scripts do
not use rclone.
### rclone and file-drop limits
A `~/.config/rclone/rclone.conf` remote is useful as documentation of the
filesdrop URL, but **public file-drop shares are upload-only**. Nextcloud allows
only **PUT, MKCOL, and MOVE** on this endpoint — not PROPFIND, GET, or LIST.
| Operation | Typical result |
| --- | --- |
| `curl -T` (backup scripts) | Works (HTTP 201) |
| `rclone lsd` / `rclone ls` | **405** — listing not allowed |
| `rclone copyto` | Often **405** after upload — rclone probes metadata the share forbids |
If you maintain a rclone remote, point it at the filesdrop base (not
`/public.php/webdav/`):
```ini
[nextcloud-backup]
type = webdav
url = https://<host>/public.php/dav/filesdrop/<share-token>/
vendor = nextcloud
user = <share-token>
pass =
```
Do not rely on rclone to verify uploads or restore from offsite copies — use
Nextcloud admin read access, the local cache under `~/.cache/railiance/backups/`,
or the restore procedure below.
A local cache of the last 7 backups of each type is kept in
`~/.cache/railiance/backups/`.