AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Attachment downloads are broken for files over 500 MiB

(#600) Bug Needs triage media self-hosting
by RexSystem edited originally by @valtteri1010 on GitHub

Summary

When increasing attachment upload limits from the admin panel to over 500 MiB, you aren't able to download files over 500 MiB even if upload worked fine. When downloading files over 500 MiB, media-proxy throws an error and rejects the download:
media-proxy-1 | {"timestamp":"2026-06-16T19:44:41.879912Z","level":"WARN","fields":{"message":"request rejected","req":"NY8KF0BHZ0Q5","kind":"attachment","method":"GET","path":"/attachments/1516471820922912790/1516508361430925312/hannah_montana_linux_x86_basic_edition.iso","query":"download=true","status":413,"duration_ms":3,"fetch_ms":0,"transform_ms":0,"nsfw_ms":0,"reason":"storage_error","source":"\"key=attachments/1516471820922912790/1516508361430925312/hannah_montana_linux_x86_basic_edition.iso err=stream too long\""},"target":"fluxer_media_proxy::request_log"}
Seems to be because of a constant MAX_MEDIA_PROXY_BYTES

Steps to reproduce

  1. Increase upload limits to 2097152000 bytes.
  2. Upload a file that is over 500 MiB.
  3. Try to download the file.

Environment

Stable Web 2026.616.45607, Linux (x86), Chrome 149.0.0.0, Locale en-GB OS: Linux 7.0.12-1-cachyos (x64) Commit: fa3e8525755dae087c03ceaf83b814cbe46c7228

2 comments

Sign in with Fluxer to comment and vote.
Comment by @cirogargatagli
RexSystem 1 vote edited originally by @cirogargatagli on GitHub
Same error for me. After investigating, I found that serve_stored_passthrough_stream() rejects any object whose size exceeds constants::MAX_MEDIA_PROXY_BYTES before attempting to stream it: 
if head.content_length > constants::MAX_MEDIA_PROXY_BYTES as u64 {
    return storage_error_response(key, StorageError::StreamTooLong);
}
MAX_MEDIA_PROXY_BYTES is currently defined as: 
pub const MAX_MEDIA_PROXY_BYTES: usize = 500 * 1024 * 1024;
Permalink
Deleted comment
Removed by moderator Rex: Removed a general status note that was posted on many GitHub threads. It no longer applies here.
Comment by @brunorsvr
RexSystem 1 vote originally by @brunorsvr on GitHub
Hi! I would like to take this one I reproduced the issue locally and confirmed the 413 on attachment downloads over 500 MiB. The limit seems to be shared between the media processing path and streamed attachment downloads, so I’m planning to keep the cap for media processing while removing it from the streaming path Mind if I take this?
Permalink