# Ingress: 413 Request Entity Too Large

**URL:** <https://community.okteto.com/t/ingress-413-request-entity-too-large/857>\
**Category:** Help\
**Created:** [June 5, 2023, 1:59pm UTC](https://community.okteto.com/t/ingress-413-request-entity-too-large/857 "2023-06-05T13:59:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![boedy](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/boedy/32/388_2.png) [@boedy](https://community.okteto.com/u/boedy)\
**Post date:** [June 5, 2023, 1:59pm UTC](https://community.okteto.com/t/ingress-413-request-entity-too-large/857/1 "2023-06-05T13:59:37Z")

</div>

I’m running Okteto self-hosted cluster on DigitalOcean

Using the public endpoints I’m not able post any files to my application. Getting the error: 413 Request Entity Too Large. I first though it was a misconfiguration of my application, but every public endpoint I send it to returns the same error.

The right annotation is applied to the ingress, so not sure what is causing it.: `nginx.ingress.kubernetes.io/proxy-body-size: 60M`

Ingress Log:  
`2023/06/05 13:50:30 [error] 167#167: *8495906 client intended to send too large body: 5023721 bytes, client: 127.0.0.1, server: ~^(?<subdomain>[\w-]+)\.dev\. ***\.com$, request: "POST /files/ HTTP/1.1", host: "api-boedy.dev.***.com"`

---

<div class="post-metadata">

**Author:** ![boedy](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/boedy/32/388_2.png) [@boedy](https://community.okteto.com/u/boedy)\
**Post date:** [June 5, 2023, 2:05pm UTC](https://community.okteto.com/t/ingress-413-request-entity-too-large/857/2 "2023-06-05T14:05:44Z")

</div>

Right after posting I found the issue:

The `okteto-wildcard` ingress in the `okteto` namespace didn’t have the correct annotation. Adding the `nginx.ingress.kubernetes.io/proxy-body-size: 200m` annotation to it fixed the issue.

I believe this can be considered a bug as there also doesn’t seem a way to add the annotation to the config: [https://artifacthub.io/packages/helm/okteto/okteto/1.8.1?modal=values](https://artifacthub.io/packages/helm/okteto/okteto/1.8.1?modal=values)

---

<div class="post-metadata">

**Author:** ![provecho](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/provecho/32/45_2.png) [@provecho](https://community.okteto.com/u/provecho)\
**Post date:** [June 12, 2023, 3:32pm UTC](https://community.okteto.com/t/ingress-413-request-entity-too-large/857/3 "2023-06-12T15:32:59Z")

</div>

Hi @boedy,

Thank you for bringing this to our attention. I’m happy to inform you that we have identified and resolved the regression issue that occurred since version 1.8.0.

We have just released version 1.9.0, which includes a fix for this problem.

You can find more details about the fix and other improvements in the [1.9 release notes](https://www.okteto.com/docs/self-hosted/install/releases#bugfixes:~:text=When%20using%20dual%20ingress%20controller).

Additionally, we will be providing a patch for the 1.8.x release with the backported fix.

Please feel free to reach out if you have any further questions.

---

<div class="post-metadata">

**Author:** ![provecho](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/provecho/32/45_2.png) [@provecho](https://community.okteto.com/u/provecho)\
**Post date:** [June 12, 2023, 3:34pm UTC](https://community.okteto.com/t/ingress-413-request-entity-too-large/857/4 "2023-06-12T15:34:48Z")

</div>

> [@boedy](#):
>
> I believe this can be considered a bug as there also doesn’t seem a way to add the annotation to the config: [okteto 1.8.1 · okteto/okteto](https://artifacthub.io/packages/helm/okteto/okteto/1.8.1?modal=values)

The current value is set to 60M, and we are seeking better ways to enable users to customize it.