Replies: 5 comments 6 replies
-
|
you can already do this, you just need to add port to your docker compose or run command like this
|
Beta Was this translation helpful? Give feedback.
-
|
Just set the env var |
Beta Was this translation helpful? Give feedback.
-
|
If using docker-compose, you can add the following to your docker-compose.yaml: The default flask port is 5000, so simply change the above to whatever you want instead. Unfortunately, it does not look like there's any way to change the stream ports via configuration variables, which means there's no control over what ports they use when I don't have time right now, but I may try to modify the environment variable list and source code to support custom ports for these if the maintainer doesn't get to it first... |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I'll give that a try. |
Beta Was this translation helpful? Give feedback.
-
|
Brute force method would be to find/replace all instances of the default port numbers with the one you want instead inside the docker, but upgrades will be annoying :D |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, upgrades would be annoying, although there's not that many.. As long as I don't reboot or bring down the docker, it should be ok. I did managed to get it to work on other ports, needed to modify the mediamtx.yaml config and also replace two instances of 8554 in ffmpeg.py (haven't bothered with the other hardcoded ports in web_ui.py since all I need is to feed my Frigate instance. But for someone who actually uses the web UI, more changes would be required. They were mostly already broken since I had non standard ports in the compose file anyways when I was in bridge mode. |
Beta Was this translation helpful? Give feedback.
-
|
Just set the env var |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that also works for Flask port, but still does not help with the actual RTSP and other video stream ports, which are hard-coded. |
Beta Was this translation helpful? Give feedback.
-
|
I agree, it would be great if these could be configured via environment like I have tried to spin the service up on multiple devices and because of RTMP or some other service utilizing one of the ports I have had a difficult time getting my environment up where I could use it in The other thing that could be nice is to be able to disable some of the stream protocols (like if we only want to use HLS or RTSP. (I am not using RTMP and would gladly disable it which would free up 1935 instead of exiting because the port is already assigned to another service). I am still getting gaps in my streams, but I think that is on wyze. I think the bridge is running as good as it can for now. |
Beta Was this translation helpful? Give feedback.
-
|
if you can use macvlan or ipvlan instead of docker bridge, this port conflict problem would go away because the container will have an IP on your same network |
Beta Was this translation helpful? Give feedback.
-
|
You can do this with My compose has: FLASK_RUN_PORT: "5001"for the env section |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
With the timeout issue going on and one of the fix being to put docker in host network mode, it'll be nice if we could configure the web-ui port to be something else than 5000.
Looks like we can already customize the streams ports (haven't yet tried, but seen the options to do it), customizing the web-ui port would be icing on the cake!
Beta Was this translation helpful? Give feedback.
All reactions