By using AWS re:Post, you agree to the Terms of Use

EC2 TCP port Connection refused

0

Hi,
i have create a new instance (ID: i-0a9d6e25034d7c41a) and added a security group with a custom TCP port (7070) in inbound trafic.
nothing happens. The port is still blocked.
Im running UFW behind, and having allowed 7070 port too.

To Action From


.......
7070 ALLOW Anywhere
7070 (v6) ALLOW Anywhere (v6)

#######################
{ Error: listen EADDRNOTAVAIL {IP}:7070
at Server.setupListenHandle [as _listen2] (net.js:1269:19)
at listenInCluster (net.js:1334:12)
at doListen (net.js:1460:7)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:744:11)
at startup (internal/bootstrap/node.js:285:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
errno: 'EADDRNOTAVAIL',
code: 'EADDRNOTAVAIL',
syscall: 'listen',
address: '{IP}',
port: 7070 }

Thank you.

asked 2 years ago45 views
1 Answer
0

Hi,

Doing a quick test to the IP address of your instance on that port I can see that it is giving a connection refused.

[ec2-user ~]$ nc -vz 18.207.237.18 7070
nc: connect to 18.207.237.18 port 7070 (tcp) failed: Connection refused

There are two possible scenarios here, the application you are using is not listening on this port or your firewall is still refusing the connections.

You can see if your application is in fact running and listening on that port by running the following command.

 sudo netstat -tulpn
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions