413 error fix. AWS Elastic Beanstalk. SSH into EC2 instance

SSH into AWS Elastic Beanstalks EC2 instance
Update nginx.conf file with client_max_body_size 20M to fix 413 error

[@pbshiver]

you are a legend thank you so much for this

[@abdellah2962]

Thank you for taking time to make this video . Your solution worked for me .

[@haykhovhannisyan8457]

Thanks for interesting step by step tutorial. Just in case that after each deployment we should do the same again if no other solution for that.

[@JS19190]

I just wanted to tell you that I tried to fix this exact problem for two days now, and finally - with the help of your video - I was able to solve it. Thanks mate, you're a lifesaver! 🦸‍♂️👍
Edit: If someone watching this is still having problems, this thread might be helpfull:
stackoverflow.com/questions/18908426/increasing-client-max-body-size-in-nginx-conf-on-aws-elastic-beanstalk

[@saganawski]

Glad it helped. Thanks for adding the link too. That should help out others

[@kairattobokelov3239]

Saved my fucking life!!! Thank you very much!

[@nicholasmagee6447]

I love you.

[@mathewsxavier1523]

He forgot to restart nginx, here is the command -> sudo systemctl reload nginx

[@1990JAF]

Thanks that did it!

[@jerrynwaeze9269]

You forgot to add "sudo service nginx reload" at the end

[@ashishwaykar2838]

these does not works for me
please help

[@vikramangadi]

Is there a way to automate this process?

[@AlexandrSargsyan]

Thanks, but after it we need restart nginx
`sudo systemctl restart nginx`

[@vickymishra3520]

i need help in aws can you plz help me