Can't start instance

Question

Can't start instance

Closed this issue 5 years ago · 12 comments

Continously complaining about redis; conn-refused

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
Emitted 'error' event at:
at RedisClient.on_error (/opt/multiparty-meeting/server/node_modules/redis/index.js:406:14)
at Socket. (/opt/multiparty-meeting/server/node_modules/redis/index.js:279:14)
at Socket.emit (events.js:198:13)
at Socket.EventEmitter.emit (domain.js:448:20)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
Container starting up...

process.env.DEBUG: undefined
config.mediasoup.logLevel: undefined
config.mediasoup.logTags: undefined
events.js:174
throw er; // Unhandled 'error' event
^

Answer 1 · 2020-04-29T18:29:26.000Z

@cemkoker Is a redis container, or local redis instance running and listening on localhost?

Answer 2 · 2020-04-29T18:31:07.000Z

no, obviously not; but i do see a 'redis.conf' in your configs; but it doesn't get installed ? (Running CentOS 7)

Answer 3 · 2020-04-29T18:32:22.000Z

try to use docker-compose up -d

Answer 4 · 2020-04-29T18:37:25.000Z

docker-compose up

Building mm
Step 1/31 : FROM node:lts-alpine AS mm-builder
ERROR: Service 'mm' failed to build: Error parsing reference: "node:lts-alpine AS mm-builder" is not a valid repository/tag: invalid reference format

Answer 5 · 2020-04-29T19:23:51.000Z

Sorry I missed to tell use docker-compose pull first.

Answer 6 · 2020-04-30T13:04:35.000Z

Thanks ! It worked ! Now i just need to solve the websocket issue

websocket.js:120 WebSocket connection to 'wss://xxx.com/socket.io/?peerId=awskomok&roomId=test&EIO=3&transport=websocket&sid=fTEiAsQKoNuUwcsyAAAF' failed: Connection closed before receiving a handshake response

Answer 7 · 2020-05-03T20:27:03.000Z

It seems firewall or something network related issue

Answer 8 · 2020-05-04T23:06:35.000Z

@cemkoker Let me know if I can help you more..

Answer 9 · 2020-05-05T10:08:15.000Z

I will close this please open a new issue if I can help you more.

Answer 10 · 2020-05-05T10:51:12.000Z

thanks; to confirm mm needs to have ports 443 and 40000-49999 UDP open correct ?

Answer 11 · 2020-05-05T11:02:31.000Z

You didn't wrote it, because maybe it is trivial that 443 is also tcp..
Ans Yes these ports are needed, and maybe tcp/80 is also good to have, but not mandatory.

Answer 12 · 2020-05-05T12:23:15.000Z

Yes because the network where i'm setting up this is very complex and has DirectAccess (so IPv6 > IPv4 translation); so WebRTC doesn't support that. Problem solved.