administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-02-03 09:45:22 +03:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Wording tweaks

Browse Source
This commit is contained in:
Blake Blackshear 2023-01-14 11:28:12 -06:00 committed by GitHub
parent 56af8e7d04
commit 613f05155a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/docs/configuration/live.md
View File

@ -19,8 +19,8 @@ Live view options can be selected while viewing the live stream. The options are
WebRTC works by creating a TCP or UDP connection on port `8555`. However, it requires additional configuration:
* For external access, over internet, setup your router to forward port `8555` to port `8555` on the Frigate device, for both TCP and UDP.
* For internal/local access, you will need to let go2rtc know your own go2rtc config:
* For external access, over the internet, setup your router to forward port `8555` to port `8555` on the Frigate device, for both TCP and UDP.
* For internal/local access, you will need to use a custom go2rtc config:
1. Create your own go2rtc config, based on [Frigate's internal go2rtc config](https://github.com/blakeblackshear/frigate/blob/dev/docker/rootfs/usr/local/go2rtc/go2rtc.yaml).
2. Add your internal IP to the list of `candidates`. Here is an example, assuming that `192.168.1.10` is the local IP of the device running Frigate:
@ -34,18 +34,18 @@ WebRTC works by creating a TCP or UDP connection on port `8555`. However, it req
- stun:8555
```
3. Place this config file at `/config/frigate-go2rtc.yaml`. Here is an example, if you run Frigate through docker-compose:
3. Mount this config file at `/config/frigate-go2rtc.yaml`. Here is an example, if you run Frigate through docker-compose:
```yaml
volumes:
- /path/to/your/go2rtc.yaml:/config/frigate-go2rtc.yaml:ro
- /path/to/your/go2rtc.yaml:/config/frigate-go2rtc.yaml
```
:::note
If you are having difficulties to make WebRTC work, and you are running Frigate through docker, you may want to try changing the container network mode:
If you are having difficulties getting WebRTC to work and you are running Frigate with docker, you may want to try changing the container network mode:
* `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. This network mode is recommended by go2rtc, but we recommend you only use it if necessary.
* `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.
:::