- Más nuevo
- Más votos
- Más comentarios
Hello.
Looking at the log, it seems that it is proxying to "http://127.0.0.1:3000/".
I believe that the problem is caused by not being able to access "http://127.0.0.1:3000/".
What kind of service is running on "http://127.0.0.1:3000/"?
Double-check your NestJS code to ensure it's configured to listen on port 3000. If not, update the code to use the correct port Log into your environment and use commands like ps aux | grep node to see if your Node.js process is running. In your EC2 console, examine the security group assigned to your Elastic Beanstalk instances.
If possible, temporarily create a very basic Node.js app (basic HTTP server) and deploy it on your Elastic Beanstalk environment. If this works, it helps isolate whether the issue is with your NestJS app or the Beanstalk configuration.
Contenido relevante
- OFICIAL DE AWSActualizada hace 9 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- ¿Cómo puedo solucionar una advertencia de estado amarillo o rojo en mi entorno de Elastic Beanstalk?OFICIAL DE AWSActualizada hace un año