Forum archive › Kubernetes & Helm Charts

Nginx Ingress returns 413 Entity Too Large

Read-only archive. These discussions are from Tracston's earlier technical forum and are kept online because the answers are still useful. New replies are closed. Need help with something like this? Talk to us.

Question 10 Jan 2023

Problem

User gets the following error from NGINX ingress configured on kubernetes cluster

Nginx Ingress returns 413 Entity Too Large

Solution

metadata:
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: “0”
nginx.ingress.kubernetes.io/proxy-read-timeout: “600”
nginx.ingress.kubernetes.io/proxy-send-timeout: “600”
name: harbor-registry
namespace: harbor-registry
spec:

Reply 1 17 Jan 2023

nginx.ingress.kubernetes.io/client-max-body-size: "0"
nginx.ingress.kubernetes.io/proxy-body-size: "0"
nginx.ingress.kubernetes.io/proxy-connect-timeout: 600s
nginx.ingress.kubernetes.io/proxy-read-timeout: 600s
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.org/client-max-body-size: "0"
nginx.org/proxy-connect-timeout: 600s
nginx.org/proxy-read-timeout: 600s

Need this fixed properly?

We do this for a living.

Kubernetes, DevOps and platform engineering, delivered in days — not another weekend lost to a stack trace.

Start a project →