1 Answer
- Newest
- Most votes
- Most comments
0
What language do you use for your backend? If it's PHP, you may be able to fix the problem by reading this https://serverfault.com/questions/543999/104-connection-reset-by-peer-while-reading-response-header-from-upstream-nginx
usually it's about nginx not being able to connect to the upstream (your backend application)
try to restart your backend, if the problem persists, look at the logs of those with whom you launched your backend, this one may not have enough RAM, in which case you will have an error 137
Did I help you?
answered a year ago
Relevant content
- asked 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 14 days ago
- How do I customize my nginx configuration to modify the "client_max_body_size" in Elastic Beanstalk?AWS OFFICIALUpdated a year ago