From d6c9538859c3478bb51aadb5800c05b6cfc74450 Mon Sep 17 00:00:00 2001 From: Juliafin Date: Fri, 14 Apr 2023 10:02:57 -0400 Subject: [PATCH] Improve documentation on web rtc (#6005) * Improve documentation on web rtc * Update docs/docs/configuration/live.md Co-authored-by: Nicolas Mowen * Specify code type in markdown * Match docker config * Add indication that there are other attributes --------- Co-authored-by: Nicolas Mowen Co-authored-by: Blake Blackshear --- docs/docs/configuration/live.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/docs/configuration/live.md b/docs/docs/configuration/live.md index 9cf30cd1a..eac8bb470 100644 --- a/docs/docs/configuration/live.md +++ b/docs/docs/configuration/live.md @@ -99,6 +99,18 @@ If you are having difficulties getting WebRTC to work and you are running Frigat - `network: host`, in this mode you don't need to forward any ports. The services inside of the Frigate container will have full access to the network interfaces of your host machine as if they were running natively and not in a container. Any port conflicts will need to be resolved. This network mode is recommended by go2rtc, but we recommend you only use it if necessary. - `network: bridge` creates a virtual network interface for the container, and the container will have full access to it. You also don't need to forward any ports, however, the IP for accessing Frigate locally will differ from the IP of the host machine. Your router will see Frigate as if it was a new device connected in the network. +If not running in host mode, port 8555 will need to be mapped for the container: + +docker-compose.yml +```yaml +services: + frigate: + ... + ports: + - "8555:8555/tcp" # WebRTC over tcp + - "8555:8555/udp" # WebRTC over udp +``` + ::: See [go2rtc WebRTC docs](https://github.com/AlexxIT/go2rtc/tree/v1.2.0#module-webrtc) for more information about this.