跳至內容

Nginx 502 Bad Gateway Error on Elastic Beanstalk Node.js Backend

0

I'm encountering a frustrating issue with my Elastic Beanstalk environment running a Node.js backend. Everything was working fine, but suddenly, I started receiving a 502 Bad Gateway error from Nginx. Here’s the relevant log entry:

2024/08/02 15:03:57 [error] 993452#993452: *3773 connect() failed (111: Connection refused) while connecting to upstream, client: 135.125.246.189, server: , request: "GET /.env HTTP/1.1", upstream: "http://127.0.0.1:8080/.env"

Details:

Environment: Elastic Beanstalk for Node.js Port Configuration: The application was running on port 8080 for last 15 days and Suddenly 502 error popped up. Recent Changes: (Include any recent changes you made, if applicable) If any further information is required, I can provide additional details. Please help out!

已提問 1 年前檢視次數 437 次
1 個回答
1
已接受的答案

The error "connect() failed (111: Connection refused) while connecting to upstream" indicates that the application is not responding. The issue is associated with the application itself. It can be because it is using a different port or it can be because the application is not running at all.

To troubleshoot, I would check the file "web.stdout.log" in Bundle logs. Also, you can try to login inside the EC2 instance ( using SSH/SSM ..) and run:

curl http://localhost:<application_port_number>

For example:

curl http://127.0.0.1:8080

if no response received, this means that the application is not running on port 8080. Then, check if it is using a different port. To verify, try running the command: Note: For NodeJS applications, I would recommend checking port 3000 and port 5000.

netstat -ltpn

And, check which port has the nodejs process listening on. If no port found associated with nodejs, then the application is down. You need to examine "web.stdout.log" for application errors.

AWS
支援工程師
已回答 1 年前
專家
已審閱 9 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。