Invalid range request
A download or preview stream rejected the Range header as invalid (416 or related). Malformed bytes syntax, multipart ranges, or out-of-bounds offsets.
Why this happens
Client/download manager sent a bad Range. Distinct from Download resume not allowed (tier toggle) and from “range not supported” on proxied remote/CDN paths.
Diagnose and fix
1. Restart the download without resume, or fix the client Range syntax (bytes=start-end).
2. If resume should work: enable Resume downloads for the tier and prefer direct download on remote nodes.
3. For proxied remote storage, see the byte-range proxied articles.
4. Preview streams (audio/video/document) can return the same invalid-range family.