[Help] - port 1935 seems to be hardcoded rather than using ENV or exposed port
See original GitHub issueDescribe the bug I have another docker using port 1935 (an RTMP server). When I change the port to say 1933 - it only exposes that port in the docker. All RTMP requests are still being sent to x.x.x.x:1935/live I’m getting all of the rtmp requests appearing in the other docker logs
I’m guessing somewhere <IP>:1935 should be <IP>:<RTMP_port>
Version of frigate latest docker
Other logs logs
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34966 [36mpath=[0m/live/back
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34968 [36mpath=[0m/live/doorbell_1
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34970 [36mpath=[0m/live/driveway
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34972 [36mpath=[0m/live/front
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34976 [36mpath=[0m/live/living_room
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34974 [36mpath=[0m/live/kitchen
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34978 [36mpath=[0m/live/side
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34988 [36mpath=[0m/live/back
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34992 [36mpath=[0m/live/doorbell_1
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:34996 [36mpath=[0m/live/driveway
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35000 [36mpath=[0m/live/front
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35004 [36mpath=[0m/live/kitchen
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35008 [36mpath=[0m/live/living_room
[90m10 Feb 21 14:57 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35012 [36mpath=[0m/live/side
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35692 [36mpath=[0m/live/doorbell_1
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35696 [36mpath=[0m/live/back
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35700 [36mpath=[0m/live/driveway
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35706 [36mpath=[0m/live/front
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35708 [36mpath=[0m/live/kitchen
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35714 [36mpath=[0m/live/living_room
[90m10 Feb 21 14:58 PST[0m [31mWRN[0m Invalid RTMP stream requested [36mclient_addr=[0m192.168.1.202:35716 [36mpath=[0m/live/side
Computer Hardware
- OS: Unraid OS
- Install method: Docker - Community Add-on
- Coral Version: PCIe
- Network Setup: Unifi APs, USG & Cloud Key Gen2+
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
Why not hard-code the port number for an application ... - Reddit
Suppose I am creating an Express app that will be dockerized. What's wrong with making it listen to a hard-coded port, e.g. 8080:...
Read more >tableau_server_linux.pdf - Tableau Help
Specify ports that should not be used during dynamic port allocation ... Star and snowflake with measures in more than one table.
Read more >What is process.env.PORT in Node.js? - Stack Overflow
If you are using this in windows machine, first you'll have to set the PORT variable as "set PORT=3300", then in the next...
Read more >Changelog - Apache Tomcat 8 (8.5.66)
Ensure that all HTTP requests that contain an invalid character in the protocol component of the request line are rejected with a 400...
Read more >Change log for 4.8.40
Port #730; Updating ose-cli-artifacts builder & base images to be consistent with ART #735 ... read etcd-operator SA token rather than using prometheus...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That makes more sense. Go ahead and open an issue.
Ok, realized I need this for the HomeAssistant component, then made me think, could it be the HA component that is requesting the streams from IP:1935?
There is nowhere in the HA component that allows the RTMP port to be configured, so assuming that is the thing that is hard coded? @blakeblackshear should I open an issue on the custom_component repo?