- We use cookies to ensure you get the best experience on our website. Read more
- Accept R-TT privacy policy
When resuming with -c or --continue , the remote server must support Range requests . If it doesn't, or if the file has changed on the server, the session may hang at 0B.
When using , encountering a status of 0B/0B during a continue or retry attempt often indicates a breakdown in communication between the client and the server. This state occurs when aria2 has initialized a download task but has not yet received any actual data or a valid file size from the remote host. Common Causes for 0B/0B Status aria2 continue download retry with 0b/0b
continous download retry with 0b/0b · Issue #209 · aria2/aria2 When resuming with -c or --continue , the
On Windows systems using legacy VFAT, aria2 might pause or show 0B while it zero-fills disk space for the file. Using --file-allocation=prealloc or moving to an NTFS/ext4 drive can mitigate this. Recommended Fixes and Configuration This state occurs when aria2 has initialized a
A common culprit is an unstable IPv6 configuration. Many users find that disabling IPv6 via --disable-ipv6=true immediately resolves stalled 0B downloads.
To break a continuous retry loop and ensure a successful resume, consider the following aria2 documentation and community-vetted flags:
If certificates cannot be verified, aria2 may loop silently. While using --check-certificate=false is a common quick fix, a more secure solution is often updating your CA bundle .