Failed to update buildpack due to 413 Request Entity Too Large Error
search cancel

Failed to update buildpack due to 413 Request Entity Too Large Error

book

Article ID: 298169

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

You tried uploading an offline buildpack and this fails with the following error
  
❯ cf create-buildpack java_buildpack_offline ~/Downloads/java-buildpack-offline-v4.64.0.zip 14

Creating buildpack java_buildpack_offline as user...

OK

 

Uploading buildpack java_buildpack_offline as user...

 1.44 MiB / 1.02 GiB [>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------]  0.14% 1s

Error unmarshalling the following into a cloud controller error: 
<html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>

TIP: A buildpack with name 'java_buildpack_offline' and nil stack has been created. Use 'cf delete-buildpack' to delete it or 'cf update-buildpack' to try again.

FAILED


Environment

Product Version: 4.0

Resolution

The error is thrown because nginx component used by cloud controller uses a configuration to request body limit in nginx's configuration property client_max_body_size which has1024MB by default. On our example above the JBP 4.64.0 is around 1090MB

You can increase the default value by TAS tile -> App developer control and increase Maximum staged droplet size

 

Find more information about parameter cloud_controller.max_file_size on the cf tile staged-config when using automation. See om cli staged-config command.

Powered by Wolken Software