Figure out what's up with OME's API port always listening on 0.0.0.0

trysdyn commented

2025-02-23 07:17:08 +00:00

Owner

For a couple versions now, I've been unable to configure the OME API to listen on localhost only. I've put in the README's security section you need to firewall the port. It's a nasty scary anti-pattern I'd like to remove.

Test OME 0.18.0 and try to find a configuration that doesn't do this and reflect it in example docs.

For a couple versions now, I've been unable to configure the OME API to listen on localhost only. I've put in the README's security section you need to firewall the port. It's a nasty scary anti-pattern I'd like to remove. Test OME 0.18.0 and try to find a configuration that doesn't do this and reflect it in example docs.

trysdyn commented

2025-03-07 05:30:20 +00:00

Author

Owner

Well that's easy. The API handler takes the same config as the global server bind. So if you're listening for RTMP/WebRTC on all interfaces (which I have to to receive RTMP traffic), your API port is listening there too.

I don't like that. The API port has auth at least, but it has no scopes or anything.

Well that's easy. The API handler takes the same config as the global server bind. So if you're listening for RTMP/WebRTC on all interfaces (which I have to to receive RTMP traffic), your API port is listening there too. I don't like that. The API port has auth at least, but it has no scopes or anything.

trysdyn closed this issue

2025-03-07 05:30:20 +00:00

Rows
Columns

Figure out what's up with OME's API port always listening on 0.0.0.0 #10