Different ports for client and server connections

[ropucyka]

Describe the feature

In example with RTMP:

We listening for incoming (push from OBS etc.) connections on 1935 port, but we awaiting for clients connections (from Internet, LAN) also on same port. - wtf?
And mediamtx configured as overridePublisher: yes by default. Oh my god.

[aler9]

Hello, the situation is the same in 99% of media servers. In order to solve your issue, you can:

• prevent unauthorized publishers from publishing to the server by turning on authentication (publishUser / publishPass)

• use two MediaMTX instances, one for publishing, that listens on a publisher-specific port of your choice, and the other for reading, that takes its streams from the first instance. Configuration of the first instance:

  rtmpAddress: :1936

  Configuration of the second instance:

  paths:
    mypath:
      source: rtsp://first-instance/mypath

[bluenviron-bot]

This discussion is being locked automatically because the last update was more than 2 years ago.

Do not use the content of this discussion as reference since it's probably outdated!

The official documentation is the only place in which you can find up-to-date answers.