Skip to content

Conversation

@ns1pelle
Copy link

@ns1pelle ns1pelle commented Nov 4, 2022

Related Issue:

New Behavior

...

Contrast to Current Behavior

...

Discussion: Benefits and Drawbacks

...

Changes to the Wiki

...

Proposed Release Note Entry

...

Double Check

  • I have read the comments and followed the PR template.
  • I have explained my PR according to the information in the comments.
  • My PR targets the develop branch.

cimnine and others added 30 commits May 25, 2024 15:24
add missing REMOTE_AUTH config options
Add xmlsec with no-binary option
Switch from Redis to Valkey and add Healthchecks
Add HTTP_PROXIES related parameters
…es-1.x

Update dependency django-storages to v1.14.4
renovate bot and others added 30 commits August 11, 2025 15:30
…out-5.x

Update actions/checkout action to v5
* Comply with all standards (RFC 3339, ISO 8601, and HTML).
* Reduce ambiguity.
* Ensure a fully compliant `org.opencontainers.image.created`. (fix artifacthub error)
Update `BUILD_DATE` format to include seconds
…inx-unit.json

The current NGINX Unit configuration in netbox-docker implicitly limits
incoming HTTP request bodies to roughly 2.5 MB. This causes file uploads
(custom scripts, attachments, etc.) to fail with HTTP 413 before they
reach Django, even when NetBox settings like FILE_UPLOAD_MAX_MEMORY_SIZE
are raised.

This change adds a settings block to docker/nginx-unit.json to raise
the default limit:

{
  "settings": {
    "http": {
      "max_body_size": 104857600
    }
  }
}

With this change, new deployments can handle uploads up to 100 MB out
of the box, aligning the container default with the capabilities of
NetBox core and preventing unexpected 413 errors.

Fixes: #897
Increase default NGINX Unit request body limit to 100 MB in nginx settings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.