v1.9.4

Changed

• The scan reports progress on one line instead of a five-line block every thirty seconds.
• Documented the error count that appears while scanning. The tool underneath counts every one-sided file as an error, so the number is the count of items found rather than a sign of trouble — and "retrying may help" does not apply to it.

A genuine failure still names its folder and says it could not be read.

v1.9.3

Update straight past 1.9.2, which was wrong.

Fixed

• Reverted 1.9.2. file not in <somewhere> is not a failure. rclone logs it for every file that is on one side and not the other — which is exactly what the delete scan is looking for, written to the log and to the candidate list in the same breath. 1.9.2 read those as unreadable folders and held back the folder containing each one, which is the parent of every deletion candidate, so the review would have shown almost nothing and every run would have reported itself failed.
• Those lines no longer reach the log. There is one per difference, thousands on a first run, and each says what the candidate list already says while reading like something went wrong.

1.9.1 stands: a folder that genuinely cannot be listed says so in its own words, and is still held back.

v1.9.2

Fixed

• Items the server names and then will not resolve are no longer offered for deletion. 1.9.1 held back folders the server said it could not list; the same underlying problem more often reports itself as file not in webdav root, once per item, with no folder-level error at all. Nothing was held back, and every one of those items went into the review as a deletion candidate.
• The folder holding an unresolvable item is now held back as a whole, items it did not complain about included. A listing that failed part way through has not shown the rest of it to be trustworthy.
• An unresolvable name directly at a pair root no longer holds back the entire pair.

If you are seeing file not in webdav root on paths with umlauts, this is the release that stops those files being proposed for deletion. The errors themselves remain until the filenames are normalised on the Nextcloud side.

v1.9.1

Fixed

• A folder that cannot be read is no longer treated as an empty one. Listing it fails, everything inside it is reported as missing from the other side, and the review then offered those files for deletion — files that were on the server the whole time. The folders that could not be read are now named in the log, and nothing inside them is proposed for deletion until they can be read again.
• The re-check that runs before a confirmed deletion applies the same rule, so a decision made earlier cannot delete through a folder that has since become unreadable.
• Applying review decisions over WebDAV. The remote side was addressed as user@host: there as well, which is an SSH address, so keeping or deleting a reviewed item could not find the server.

If you have been seeing error reading source directory on folders with umlauts, this is the release that stops those folders being mistaken for empty ones.

v1.9.0

Changed

• A run that fails on individual items now finishes the rest of them. It names what it could not handle, carries on to the remaining folder pairs, and reports the run as failed at the end. Until now the first unreadable path stopped everything, so one file could block a whole library.
• A failure that cannot name any item — a wrong address, a refused login — still ends the run immediately, because there is nothing to carry on with.
• The last successful sync is no longer recorded when items failed.

If you are seeing "file not in webdav root"

That is a filename stored in the wrong Unicode form: NFD, as a Synology or a Mac writes it, where Nextcloud expects NFC. Übungen looks identical either way and is different bytes, and Nextcloud will hand back a path it then refuses to accept.

It is a problem in the files rather than in this app. See the documentation for how to normalise them.

v1.8.2

Added

• .DAV/ to the default excludes. WebDAV clients leave that folder behind as their own bookkeeping, so it exists on one side and never the other, and turns up as a deletion candidate for ever. It joins .stfolder and @eaDir, which are there for the same reason.

v1.8.1

Fixed

• Excluded folders are now genuinely skipped over WebDAV, instead of being walked and then discarded. rclone only avoids descending into a folder for a rule ending in a slash; the rules added in 1.7.6 left out that form, so an excluded folder still cost a full listing every run — and could still report errors from inside itself.

Include rules gain the same form, so a whitelist can prune what it does not name.

v1.8.0

Added

• Parallel WebDAV requests under Advanced, default 16 (was a fixed 8). A share has to be listed one folder at a time, so scanning is bound by round trips rather than bandwidth, and running more at once is the most effective change available. Lower it if your server struggles.

Changed

• Copying a confirmed list of files over WebDAV no longer lists the destination first. The list already names every file to move, so that traversal was the whole cost of the operation and bought nothing.

The SSH path is unchanged — listing there is a single round trip and none of this applies.

v1.7.7

Fixed

• Removed the Config file "/root/.config/rclone/rclone.conf" not found - using defaults notice from every WebDAV command. The backend is configured through the environment on purpose, so there is nothing to put in a config file; rclone now gets an empty one to find.

v1.7.6

Fixed

• Skip within this pair and the global exclude list were ignored over WebDAV. The settings are written the way rsync reads them, where excluding Anna excludes the folder and everything in it; rclone reads a bare name as a file pattern, so those lines matched nothing and the folders synced anyway. Each pattern is now written in both forms.
• An include list over WebDAV blocked less than it should have, for the same reason.

The SSH path is unchanged.