starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Uploading image gives 413 Request Entity Too Large error #1353

New Issue
Closed
opened 2025-12-29 16:31:42 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:31:42 +01:00
Owner
Copy Link

Originally created by @matt852 on GitHub (Oct 25, 2017).

Issue type

[ ] Feature request
[X] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.6
  • NetBox version: 2.2.1

Description

When trying to upload a 2.4Mb JPEG file and attach it to a rack, I get a "413 Request Entity Too Large" error. If this is expected, I recommend redirecting to a 413 error page, with information on file size limits for uploads. Screenshot of error is attached.

screen shot 2017-10-25 at 9 45 32 am
Originally created by @matt852 on GitHub (Oct 25, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### Issue type [ ] Feature request <!-- Requesting the implementation of a new feature --> [X] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * Python version: 2.7.6<!-- Example: 3.5.4 --> * NetBox version: 2.2.1<!-- Example: 2.1.3 --> <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description When trying to upload a 2.4Mb JPEG file and attach it to a rack, I get a "413 Request Entity Too Large" error. If this is expected, I recommend redirecting to a 413 error page, with information on file size limits for uploads. Screenshot of error is attached. <img width="1435" alt="screen shot 2017-10-25 at 9 45 32 am" src="https://user-images.githubusercontent.com/536467/32002093-9b83e1de-b969-11e7-9f0d-0f8db5960482.png">
adam closed this issue 2025-12-29 16:31:42 +01:00
adam commented 2025-12-29 16:31:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 25, 2017):

This is a configuration of your HTTP daemon and is not controlled by NetBox. For example, you can increase the max request size for nginx by setting the client_max_body_size parameter (more info). The ideal setting will depend on your environment.

@jeremystretch commented on GitHub (Oct 25, 2017): This is a configuration of your HTTP daemon and is not controlled by NetBox. For example, you can increase the max request size for nginx by setting the `client_max_body_size` parameter ([more info](https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/)). The ideal setting will depend on your environment.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1353
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?