[Self-hosted] Large video upload metadata unavailable

(#721) Bug Closed: Fixed media self-hosting

Summary

When uploading larger video files on self hosted instance, they get uploaded as plain files instead of an mp4 file that can be viewed in fluxer. The video in question was around 700mb. I have updated the reverse proxies as well as config limit to allow up to 1G and it upload itself finishes but not as a reproducible video. I've tried some uploads around 100/200mb and they seemed to be recognized as mp4 and play fine on the chat.

Steps to reproduce

  1. Go into a community general chat
  2. Upload file
  3. select a large file (500+ mb)

Environment

Fluxer running on: Ubuntu server 26.04 2026.702.163118 Browser session: Helium Fedora 44

Logs or screenshots

Logs with filenames changed:
{
  "level": "error",
  "time": "2026-07-10T20:25:21.489Z",
  "service": "fluxer-api",
  "env": "production",
  "status": 400,
  "statusText": "Bad Request",
  "errorBody": "Bad Request",
  "body": {
    "type": "upload",
    "upload_filename": "8f3b1d6e-2a74-4c89-9e12-5a1f7d93c4b8",
    "filename": "file.mp4",
    "nsfw": "allow",
    "version": 2
  },
  "endpoint": "http://media-proxy:8080/_metadata",
  "msg": "Media proxy request failed"
}

{
  "level": "warn",
  "time": "2026-07-10T20:25:21.490Z",
  "service": "fluxer-api",
  "env": "production",
  "context": "message_attachment",
  "attachmentIndex": 0,
  "uploadFilename": "8f3b1d6e-2a74-4c89-9e12-5a1f7d93c4b8",
  "filename": "file.mp4",
  "msg": "Attachment media metadata unavailable; storing attachment as a plain file"
}

{
  "level": "error",
  "time": "2026-07-10T20:25:28.442Z",
  "service": "fluxer-api",
  "env": "production",
  "error": {
    "type": "Error",
    "message": "Command failed: ffmpeg -hide_banner -loglevel warning -i /tmp/input.mp4 -map 0 -map_metadata -1 -map_metadata:s -1 -map_metadata:c -1 -map_chapters -1 -c copy -y /tmp/output.mp4\n[NULL @ 0x5eb632fdfe40] Unable to find a suitable output format for '/tmp/output.mp4'\n/tmp/output.mp4: Invalid argument\n",
    "stack": "Error: Command failed: ffmpeg -hide_banner -loglevel warning -i /tmp/input.mp4 -map 0 -map_metadata -1 -map_metadata:s -1 -map_metadata:c -1 -map_chapters -1 -c copy -y /tmp/output.mp4\n[NULL @ 0x5eb632fdfe40] Unable to find a suitable output format for '/tmp/output.mp4'\n/tmp/output.mp4: Invalid argument\n\n    at genericNodeError (node:internal/errors:985:15)\n    at wrappedFn (node:internal/errors:539:14)\n    at ChildProcess.exithandler (node:child_process:417:12)\n    at ChildProcess.emit (node:events:509:28)\n    at maybeClose (node:internal/child_process:1124:16)\n    at ChildProcess._handle.onexit (node:internal/child_process:306:5)",
    "code": 1,
    "killed": false,
    "signal": null,
    "cmd": "ffmpeg -hide_banner -loglevel warning -i /tmp/input.mp4 -map 0 -map_metadata -1 -map_metadata:s -1 -map_metadata:c -1 -map_chapters -1 -c copy -y /tmp/output.mp4",
    "stdout": "",
    "stderr": "[NULL @ 0x5eb632fdfe40] Unable to find a suitable output format for '/tmp/output.mp4'\n/tmp/output.mp4: Invalid argument\n"
  },
  "contentType": "video/mp4",
  "sourceBucket": "fluxer-uploads",
  "sourceKey": "8f3b1d6e-2a74-4c89-9e12-5a1f7d93c4b8",
  "msg": "Failed to strip attachment media metadata"
}

1 comment

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Fixed
Fixed in the self-hosted media-proxy 2026.1011.113357: large videos are probed from disk instead of memory, so their metadata is read.
Deleted comment
Removed by moderator Rex: Removed a general status note that was posted on many GitHub threads. It no longer applies here.