EXTERNAL_IPV4 is actually the address assigned to the external interface, not external address globally

[vanindm]

=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.