Downloads of very large files (40GB+) stall at 0 bytes/s on self-hosted instances

### 👟 Reproduction steps 1. Set up Appwrite 1.8.0 on a self-hosted server (Docker). 2. Upload a very large file (e.g., a 40GB ZIP archive) using chunked upload via any SDK. 3. Ensure the file is marked as 'Available' in the Appwrite Console. 4. Attempt to download the file via the Appwrite Console 'Download' link or directly via the API endpoint /v1/storage/buckets/{bucketId}/files/{fileId}/download. ### 👍 Expected behavior The download should initialize and start streaming data to the client, even for files exceeding 40GB. ### 👎 Actual Behavior - The browser enters a perpetual loading state. - Download managers/tools (wget, curl) connect successfully and receive headers (often 200 OK or 206 Partial Content), but the data transfer stays at 0 Byte/s. - Eventually, the request results in a 504 Gateway Timeout. - The appwrite container logs remain completely silent during the download attempt, while Traefik logs show the request arriving but stalling during the hand-off. I've tested this by bypassing my external proxy and hitting the Traefik/Appwrite port directly—the behavior remains the same. Since the appwrite container doesn't log anything, it appears the request is being buffered or dropped at the entry level (Traefik or Swoole) before the Appwrite logic can start the stream. Other users have reported similar issues where PHP memory limits or output buffering seem to interfere with massive outbound streams. ### 🎲 Appwrite version Version 1.8.x ### 💻 Operating system Linux ### 🧱 Your Environment - Appwrite Version: 1.8.0 / 1.8.1 - Proxy Setup: Traefik (default) + Nginx Proxy Manager (optional, issue persists even when bypassing NPM and accessing Traefik/Appwrite IP:PORT directly). - Customized .env: _APP_STORAGE_LIMIT=50000000000, _APP_STORAGE_PREVIEW_LIMIT=50000000000, _APP_STORAGE_ANTIVIRUS=disabled - Range Requests: Verified working (Header 206 returned via curl -I), but payload never follows. ### 👀 Have you spent some time to check if this issue has be…