|
I'm playing around with Node.js and socket.io and my application doesn't seem to like to be hosted on a particular port which I had opened up on my dedicated IP address for this purpose (we'll call it port 12345). If I use port 12345 for even one of the sample socket.io applications, it gives me this in the console: If I use other ports (even adding or subtracting one to the desired port - such as 12344 or 12346) it seems to work with my socket.io application (no error), except those ports aren't accessible to any remote connections. Is there a way I can tell what is running on a specific port and stop/remove/ask support about it, or do I need to get another port opened up? asked 10 Mar '13, 16:09 pope |
|
To see what application and its PID I use this command, Where XXXX is the port number you are looking for, it will have output which look like this, You could than kill the app if it is still running with like this, If you need remote access on this port you must contact us with a support ticket so we can open the port in the firewall. answered 10 Mar '13, 18:00 johns ♦♦ Thanks, it turned out to be a typo in my application code. I was using weird port numbers because of it and this helped me see that right away.
(10 Mar '13, 20:49)
pope
|
|
if the node.js socket is 21095 and you are getting EADDRINUSE error: type this fuser -k 21095/tcp (kills process using that socket) Then run your ./bin/node tcp_server.js and the prompt should be sitting there listening answered 07 Mar '15, 03:13 d3nd0g69 |
