I got this error when run socket.io in docker

Question

Error:

events.js:167
node_app_1  |       throw er; // Unhandled 'error' event<br>
node_app_1  |       ^
node_app_1  | Error: listen EADDRNOTAVAIL 50.177.55.2:3000<br>
node_app_1  |     at Server.setupListenHandle [as _listen2] (net.js:1269:19)<br>
node_app_1  |     at listenInCluster (net.js:1334:12)<br>
node_app_1  |     at GetAddrInfoReqWrap.doListen [as callback] (net.js:1460:7)<br>
node_app_1  |     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:62:10)<br>
node_app_1  | Emitted 'error' event at:<br>
node_app_1  |     at emitErrorNT (net.js:1313:8)<br>
node_app_1  |     at process._tickCallback (internal/process/next_tick.js:63:19)<br>

Eranga Heshan · Answer 1 · 2021-05-20T12:22:39.883

0

Update:

Change your socker-io server's IP to 127.0.0.1

Your app is trying to listen on port 3000 and I believe it is already being used.

If you have some other service running on this port, you will either have to change the port of your socket-io server or follow the following process to kill the process that is already listening on port 3000.

Type the following in your terminal,

lsof -i:3000

It will show you the process that is listening to that port. Then you can kill that process using its process ID (PID)

kill -9 <PID>

edited May 20 '21 at 12:22

answered May 20 '21 at 11:07

Eranga Heshan

5,133
4
25
48

thank's for replay but the the port 3000 used only for this socket.io – hmz 4dev May 20 '21 at 11:37
1

Did you try to kill it and restart your docker container? – Eranga Heshan May 20 '21 at 11:38
yeah, the same . – hmz 4dev May 20 '21 at 11:40
Could you attach the result of the terminal command `sudo lsof -i:3000`? – Eranga Heshan May 20 '21 at 11:46
You're running `netstat` because `lsof` is not working for you? What is your machine? – Eranga Heshan May 20 '21 at 11:51
I run it in linux – hmz 4dev May 20 '21 at 12:02
Can you show the output of `sudo lsof -i:3000` then? – Eranga Heshan May 20 '21 at 12:05
`hamza@vps-656a1918:~$ sudo lsof -i:3000 hamza@vps-656a1918:~$` – hmz 4dev May 20 '21 at 12:17
return nothing . – hmz 4dev May 20 '21 at 12:18
Oh wait, you need to change the IP to `127.0.0.1`. Your current value is `50.177.55.2` – Eranga Heshan May 20 '21 at 12:21
i used for production env i can't access if i use 127.0.0.1 – hmz 4dev May 20 '21 at 12:26
It's fine because in production as well you will run a docker container, right? Then it is still going to be `127.0.0.1` – Eranga Heshan May 20 '21 at 12:28
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://127.0.0.1:3000/socket.io/?EIO=4&transport=polling&t=Nc9mV3n. (Reason: CORS request did not succeed). – hmz 4dev May 20 '21 at 12:32
Does this comes when you try to connect to the server from a soket-io client? – Eranga Heshan May 20 '21 at 12:48
You need to allow CORS in your socket-server then. Check this [link](https://stackoverflow.com/questions/24058157/socket-io-node-js-cross-origin-request-blocked). But setting up CORS in your server is a different problem. This is fixed for you now – Eranga Heshan May 20 '21 at 12:52
ok, i will read it and if is done, i accept your answer – hmz 4dev May 20 '21 at 12:59

I got this error when run socket.io in docker

1 Answers1

Update: