The remote server returned an error: (413) Request Entity Too Large..

[David]

Hi,

I'm trying to push packages using nuget.exe. I've copied the command from the UI, it looks like this : NuGet.exe push "C:\PackageName.1.6.17.nupkg" myapikeyhere -Source https://thenugetserver.com/nuget/nuget

I always get the error:

Failed to process request. 'Request Entity Too Large'. The remote server returned an error: (413) Request Entity Too Large..

So I have an APIKey set on the nuget feed. I gave the rights to anonymous to all the Feeds permissions. I have pretty much all the upload limit variables set up to maximum in the webconfig (httpRuntime maxRequestLength, requestLimits maxAllowedContentLength and even for bindings).

Not sure if the error is relevant or if it's misleading and there is something else wrong ? I can list packages... but I can't push them.

Thanks.

Product: ProGet
Version: 4.0.10

[David]

Found the solution to my problem:

appcmd.exe set config "ProGet" -section:system.webServer/serverRuntime /uploadReadAheadSize:"2147483647"  /commit:apphost

[Matthew Monahan]

I ran into this issue when deploying to kubernetes and found that the solution was to add an annotation to my Ingress that told nginx to allow the 'proxy-body-size' to be bigger.

Ex:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: proget-ingress
  namespace: proget
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: "100m" #This part
spec:
  rules:
  - host: hostname.my.host.com
    http:
      paths:
      - backend:
          serviceName: proget
          servicePort: 80

[Banyan S]

@Matthew -- how did you set this up ProGet in Kubernetes? Did you use a helm package?

Could you share your repository or kubernetes files? Or Helm package?

[joe.spann_7401]

Yep, you are awesome. I know this is an old post, but it was my issue as well. Using a nginx proxy for the server.
Thank you.