EXTERNAL_IPV4 is actually the address assigned to the external interface, not external address globally
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- documentation
Research direction
Search the repository documentation and configuration references for EXTERNAL_IPV4, since no specific file is named in the issue. Clarify that it must be an address assigned to the server's external interface, not its globally reachable address, and consider the reported 10.0.0.100 example; done when the setting's expected value is unambiguous.
Written by the indexing model from the issue text.
Description
=webrtc-sfu-1 | {"level":50,"time":"2026-02-05T15:11:03.451Z","pid":31,"hostname":"[REDACTED]","mod":"core","error":{"stack":"Error: port bind failed due to address not available [protocol:udp, ip:'1.1.1.1', port:24886, attempt:1/8192] [method:router.createWebRtcTransport]\n at Channel.processResponse (/app/node_modules/mediasoup/node/lib/Channel.js:260:33)\n at Socket.<anonymous> (/app/node_modules/mediasoup/node/lib/Channel.js:79:34)\n at Socket.emit (node:events:519:28)\n at Socket.emit (node:domain:489:12)\n at addChunk (node:internal/streams/readable:561:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n at Readable.push (node:internal/streams/readable:392:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","message":"MEDIA_SERVER_GENERIC_ERROR","code":2019,"details":"port bind failed due to address not available [protocol:udp, ip:'1.1.1.1', port:24886, attempt:1/8192] [method:router.createWebRtcTransport]","stackWasLogged":true},"msg":"User: publish failed due to MEDIA_SERVER_GENERIC_ERROR"}
``
(Assuming 1.1.1.1 to be the global address of server)
Changing 1.1.1.1 to, let's say, 10.0.0.100 (which is address of server in local network), fixes the issue (quite obviously)
In my opinion, mentioning that in documentation should be necessary.
- Dominant language
- Shell
- Stars
- 436
- Forks
- 274
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bigbluebutton/docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
bigbluebutton/docker#395 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bigbluebutton/docker#382 · 5 comments · 1 reaction ·
-
error in README.mdOpen
Difficulty 1/5 Under an hour Newbie friendliness 65/100
bigbluebutton/docker#294 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
bigbluebutton/docker#396 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bigbluebutton/docker#392 ·
All issues in bigbluebutton/docker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nolabs-ai/nono-packs#44 ·
Maintainers usually reply within 1 day
-
easy low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-nudge/opentemplate#185 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
omacom/omarchy#14030 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel-labs/skills#2360 ·
Maintainers usually reply within 2 days