Upload Size Limits for Large Scan Files (Pro)
A large scan file can be rejected at two points on a Docker Compose deployment: the application’s own limit, and the nginx that ships in front of it. The error you get tells you which one you hit. Running Kubernetes? See Upload Size Limits for Large Scan Files for the Helm chart, which adds ingress and import-route limits that do not apply here.
Which limit am I hitting
| What you see | Where it came from |
|---|---|
Report file is too large. Maximum supported size is N MB | The application limit, reported by DefectDojo itself |
A plain 413 Request Entity Too Large, unstyled, with no DefectDojo page around it | The nginx that ships with the deployment rejected the request before it reached the application |
The application limit
DefectDojo enforces a maximum scan file size of its own, and rejects anything larger with a message naming the current limit. It defaults to 100 MB. On Docker Compose, set the DD_SCAN_FILE_MAX_SIZE environment variable, in megabytes, through the CLI, then restart:
dojo-compose-cli environment add DD_SCAN_FILE_MAX_SIZE=200
dojo-compose-cli app restartRun dojo-compose-cli environment add --help for the exact syntax your CLI version expects.
The nginx ceiling
Compose deployments have no ingress controller, so the ingress limit that Kubernetes deployments raise does not apply. Instead, the nginx that ships in the deployment caps request bodies at 800 MB, which is the practical ceiling, and the application limit above applies on top of that.
Raising the nginx cap means changing a file that ships with the deployment, and those files are replaced when you upgrade rather than preserved like your customizations directory. Contact support before changing it, so the change does not disappear at the next upgrade.
Questions or support
If uploads still fail after raising the limit that matches your symptom, collect the response your client received and the nginx logs covering the attempt, then contact .