Problem category
Backup
Protect data. Verify recovery.
Immich Upload Fails Through Cloudflare Tunnel While a Trusted Non-Tunnel Path Works
Compare the same Immich upload over a trusted non-Tunnel path and a Cloudflare Tunnel hostname, then classify a Cloudflare-attributed 413, a 524 timeout, a Tunnel origin 502, or an origin-side proxy failure before changing configuration.
Immich Mobile Backup Stalls or Uploads Keep Failing
Verify whether expected originals are actually missing server-side on Immich 3.1.0, then separate album selection, background constraints, proxy path, storage, and dependency failures before touching any data or database.
restic Reports the Repository Is Already Locked
Capture the restic exit code, separate a still-running lock from a stale one, then use the documented unlock command without disabling locking for write operations.
Syncthing Reports “Folder Marker Missing”
Treat .stfolder as a safety guard: prove the configured path, expected filesystem, and expected local data are present before recreating the marker or considering a folder reset in Syncthing 2.1.3.
Synology Hyper Backup Insufficient Destination Quota
Inspect retained versions and destination usage before choosing a capacity or retention procedure, without deleting recovery points as a diagnostic test.
Synology Hyper Backup Restore Only After an Integrity Check
Confirm the integrity-check finding, preserve recovery options, and identify the evidence needed for a destination-specific recovery plan.
Synology Hyper Backup Destination Offline over Tailscale
Separate the Tailscale path from the Hyper Backup Vault service when a remote Synology destination over Tailscale cannot connect. Test from the source NAS, then the exact address, service port, and DSM 7 outbound access.
Synology Hyper Backup Taking Longer Than Expected
Check task state, logs, NAS resources, and destination-specific signals when Hyper Backup is still running without a confirmed error.
Synology Hyper Backup Task Suspended After Interruption
Distinguish a resumable interruption from cancellation, identify the interruption context, and preserve the right backup-version expectations.