Replies: 1 comment 6 replies
-
|
Port 1935 in the default configuration is used by mediaMTX for RTMP. rtmpAddress: :1935 Check the rtmp section of the configuration for both instances., if you don't use rtmp try set rtmp: false in both configuration |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Question
Version v1.19.1
Running on command line
UPDATE - 2026-06-18 20:05 MST (2026-06-19 02:05 UTC): Many additions/clarifications have been made in the preamble of this post.
I am using mediamtx in an application I am building for macos, to capture HEVC streams from surveillance cameras on my local network, and stream over tcp so I can access the stream using WebRTC and play in a
To test this I have been running mediamtx directly from the command line. What I have found is that I can start one instance of mediamtx using a given configuration (simulating some other app's instantiation), and it works fine. However, if I attempt to start another instance of mediamtx using a different configuration (different port numbers, etc, simulating instantiation by my app) the second instance of mediamtx immediately exits with an error relating to port conflict.
So my question is, is it not possible to run 2 instances of mediamtx on the same device?
Here are my configs and the output for each instance started with each config.
First I will give the simpler configuration as I don't think this involves a bug, but is due to my lack of knowledge. I will include output with
logLevelset todebug, anddumpPacketsset totruefurther down.Note, either one of these configs will work as long as there are no other instances of mediamtx running.
Assume that I will not have control over how the first instance is configured. I would need a configuration for the second instance (ie, the configuration I would use in my app) that would be able to launch, regardless (mostly) of how the the first instance is configured.
Config:
Output:
Config:
Output:
Here is the output with same configurations, but with
logLevelset todebug, anddumpPacketsset totrue:First instance:
Second instance:
Beta Was this translation helpful? Give feedback.
All reactions