How to fix 413 Request Entity Too Large – harbor

C:\Users\*****>docker push  ******/wordpress/wordpress:latest
The push refers to repository [******/wordpress/wordpress]
4c9bd1a5ba3e: Pushed
061bdd304944: Pushed
5daef51ff952: Pushing [==================================================>]  70.38MB/70.38MB
5aaeb76a19b4: Pushed
ffc3760f2e73: Pushed
2c0cc52b0ca0: Pushed
20ad5f45fc5c: Retrying in 1 second
43718d2820ea: Retrying in 1 second
90883efd6334: Pushed
42e0acc99841: Pushed
11141e153ae2: Pushed
00b236d97b2a: Retrying in 3 seconds
3a15f0030861: Pushed
0c9fda56831c: Retrying in 3 seconds
7219ec818434: Waiting
dda304899549: Waiting
390716dfffcd: Waiting
030e470e5f11: Waiting
19adf6ebb0bd: Waiting
612b0f444e86: Waiting
32148f9f6c5a: Waiting
unknown: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.27.0</center>
</body>
</html>

This issue was due to the Nginx ingress upload body limit. To fix this, add the two annotations mentioned below.

nginx.ingress.kubernetes.io/proxy-body-size: "10240m"
nginx.org/client-max-body-size: "10240m"

Change the size based on your requirement

e.g:
1024m = 1GB

⚠️Note: This is for ingress based on Nginx Ingress Controller

Leave a Reply

Your email address will not be published. Required fields are marked *