meething / meething/meething-docker

WebRT problem with port bind? // Documentation missing ports / range?

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
17
Forks
2
PR merge metrics
No merged PRs in 30d

Description

First try to deploy meething-docker.

config

module.exports = {
  apps : [{
    name: 'meething',
    script: '/meething/src/app.js',
    watch: './meething/src',
    env : {
      SSL : false,
      SSLKEY : '/certs/privkey.pem',
      SSLCERT  : '/certs/fullchain.pem',
      DEBUG : false
    }
  },{
    name: 'mediasoup',
    script: '/mediasoup/main.js',
    env : {
      SSL : false,
      SSLKEY : '/certs/privkey.pem',
      SSLCERT  : '/certs/fullchain.pem',
      DEBUG : false
    }
  },{
    name: 'gunsocket',
    script: '/gun/server.js',
    env : {
      SSL : false,
      SSLKEY : '/certs/privkey.pem',
      SSLCERT  : '/certs/fullchain.pem',
      PORT : 8765,
      DEBUG : false
    }
  }]
};

Error message on login / connect

protoo connection request [peerId:<CLIENT_IP>, address:/?roomId=Wupudaipo-Catherine-Fuudsev&peerId=99128d3c-5b72-4608-a023-f3041a8a29d6, room:%s]
new room stat Wupudaipo-Catherine-Fuudsev 99128d3c-5b72-4608-a023-f3041a8a29d6 { peer: 1, transport: 0, transports: [] }
request:getRouterRtpCapabilities
request:createWebRtcTransport
request failed:Error: port bind failed due to address not available [transport:udp, ip:'<SERVER_IP>', port:20785, attempt:1/10000]
    at Channel._processMessage (/mediasoup/node_modules/mediasoup/lib/Channel.js:206:37)
    at Socket.<anonymous> (/mediasoup/node_modules/mediasoup/lib/Channel.js:68:34)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:271:9)
    at Socket.Readable.push (_stream_readable.js:212:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:186:23) {
  [stack]: "Error: port bind failed due to address not available [transport:udp, ip:'<SERVER_IP>', port:20785, attempt:1/10000]\n" +
    '    at Channel._processMessage (/mediasoup/node_modules/mediasoup/lib/Channel.js:206:37)\n' +
    '    at Socket.<anonymous> (/mediasoup/node_modules/mediasoup/lib/Channel.js:68:34)\n' +
    '    at Socket.emit (events.js:315:20)\n' +
    '    at addChunk (_stream_readable.js:295:12)\n' +
    '    at readableAddChunk (_stream_readable.js:271:9)\n' +
    '    at Socket.Readable.push (_stream_readable.js:212:10)\n' +
    '    at Pipe.onStreamRead (internal/stream_base_commons.js:186:23)',
  [message]: "port bind failed due to address not available [transport:udp, ip:'<SERVER_IP>', port:20785, attempt:1/10000]"
}
request:createWebRtcTransport
request failed:Error: port bind failed due to address not available [transport:udp, ip:'<SERVER_IP>', port:27500, attempt:1/10000]
    at Channel._processMessage (/mediasoup/node_modules/mediasoup/lib/Channel.js:206:37)
    at Socket.<anonymous> (/mediasoup/node_modules/mediasoup/lib/Channel.js:68:34)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:271:9)
    at Socket.Readable.push (_stream_readable.js:212:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:186:23) {
  [stack]: "Error: port bind failed due to address not available [transport:udp, ip:'<SERVER_IP>', port:27500, attempt:1/10000]\n" +
    '    at Channel._processMessage (/mediasoup/node_modules/mediasoup/lib/Channel.js:206:37)\n' +
    '    at Socket.<anonymous> (/mediasoup/node_modules/mediasoup/lib/Channel.js:68:34)\n' +
    '    at Socket.emit (events.js:315:20)\n' +
    '    at addChunk (_stream_readable.js:295:12)\n' +
    '    at readableAddChunk (_stream_readable.js:271:9)\n' +
    '    at Socket.Readable.push (_stream_readable.js:212:10)\n' +
    '    at Pipe.onStreamRead (internal/stream_base_commons.js:186:23)',
  [message]: "port bind failed due to address not available [transport:udp, ip:'<SERVER_IP>', port:27500, attempt:1/10000]"
}
request:join

Do I need more ports mapped to the docker container like 27500/udp? Haven't found such an information in readme file?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The README is the named documentation entry point; start by checking its Docker port-mapping instructions against the shown configuration and the mediasoup bind errors on ports 20785 and 27500. Done means documenting the required container port or port range, including UDP mapping, if that is the supported deployment setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript, node.js
Domain
devops, documentation, networking
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.