include conf.d/elasticbeanstalk/*.conf Įverything should work but it isn't and I'm still seeing the error in /var/log/nginx/error.log complaining that it got a request that was too large from the loadbalancer. Given the following entry in /etc/nginx/nf platform directory with my, I can see the file being copied to /etc/nginx/conf.d/elasticbeanstalk/ on the EC2 instance managed by Beanstalk. Created a file 01_body_nf with the content below: client_max_body_size 10M Created a directory structure as follow. I'm using Amazon Linux AMI and hence I did the following: Since Nginx is managed by Beanstalk, I am trying to update the limit via. I looked around on the internet and learned that this issue is caused by Nginx and the solution is to increase the client_max_body_size. I'm seeing a bunch of "client intended to send too large body" errors on image upload. Setting client_max_body_size 0 allows users to push repositories of any size.įinal configuration (usually the nf file is placed at /etc/nginx/nginx.I have a dockerized Django app running on Elastic Beanstalk environment that allows users to upload images. Pushing a 1.2GB repository fails with the final failure in the output above, where nginx complains about the the data being over 1GB. By setting client_max_body_size 1024m on 443, pushing a 650MB repository succeeds. Without the client_max_body_size on the 443 server entry, pushing dies basically immediately for anything not trivially-sized because the default limit of 1M is applied. Request: "POST /scm/qa/test-huge.git/git-receive-pack HTTP/1.1", host: "" Diagnosis
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |