By default, when using nginx reverse proxy to upload more than 2MB files, an error 413 request entity too large will be reported. To solve this problem, it is very simple to modify the configuration of client_ max_ body_ The size value is enough

Modify nginx.conf

If you need to upload a larger file, the client_ max_ body_ The size can be changed to a larger value. Here it is changed to 10MB

Restart nginx

Read More:

• Nginx modifies the front end request size limit (413 request entity too large)
• The file server reports an error of 413, and the file uploaded by nginx reports an error of 413 request entity too large
• IIS “Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long.”
• Nginx startup error: nginx: [error] open() “/ var / run / nginx/ nginx.pid The solution of “failed (2: no such file or directory)”
• Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long
• nginx: [error] open() “/usr/local/nginx/logs/nginx.pid“ failed (2: No such file or directory)
• nginx: [error] open() "/var/run/nginx/nginx.pid" failed (2: No such file or directory)
• mysql5.7.26：[ERR] 1118 – Row size too large (＞ 8126)
• Nginx error: nginx: [error] invalid PID number “” in “/run/nginx.pid”
• Flume receives an error when a single message is too large
• nginx: [error] invalid PID number ““ in “/data/nginx/logs/nginx.pid“
• Error in plot.new() : figure margins too large
• Update project manually_ Solution of too large jar package in springboot
• Kibana access error: data too large [How to Solve]
• /var/run/nginx/nginx.pid” failed (2: No such file or directory)
• nginx: [error] open() “/usr/local/var/run/nginx.pid” failed (2: No such file or directory)
• Java long type error: error: integer number too large
• circuit_breaking_exception,“reason“:“[parent] Data too large, data for [＜http_request＞]
• The sparse matrix of R language is too large to be used as.matrix
• nginx: [error] open() “/run/nginx.pid” failed (2: No such file or directory)