diff --git a/docs/docs/configuration/advanced/system.md b/docs/docs/configuration/advanced/system.md index 171ff97150..71ef01234c 100644 --- a/docs/docs/configuration/advanced/system.md +++ b/docs/docs/configuration/advanced/system.md @@ -233,18 +233,29 @@ Some labels have special handling and modifications can disable functionality. ## Network Configuration -Changes to Frigate's internal network configuration can be made by bind mounting nginx.conf into the container. For example: +Frigate exposes a few networking options. IPv6 and the listen ports are set in the `networking` configuration (or from the Settings UI); more advanced changes require [customizing the bundled Nginx configuration](#customizing-the-nginx-configuration). + +### Enabling IPv6 + +By default Frigate listens on IPv4 only. To also listen on IPv6 — on port `5000`, and on `8971` when TLS is configured — enable it in the `networking` configuration. + + + + +Navigate to and enable **IPv6**. + + + ```yaml -services: - frigate: - container_name: frigate - ... - volumes: - ... - - /path/to/your/nginx.conf:/usr/local/nginx/conf/nginx.conf +networking: + ipv6: + enabled: true ``` + + + ### Listen on different ports You can change the ports Nginx uses for listening. The internal port (unauthenticated) and external port (authenticated) can be changed independently. You can also specify an IP address using the format `ip:port` if you wish to bind the port to a specific interface. This may be useful for example to prevent exposing the internal port outside the container. @@ -278,6 +289,20 @@ This setting is for advanced users. For the majority of use cases it's recommend ::: +### Customizing the Nginx configuration + +More advanced changes to Frigate's internal network configuration can be made by bind mounting your own `nginx.conf` into the container. For example: + +```yaml +services: + frigate: + container_name: frigate + ... + volumes: + ... + - /path/to/your/nginx.conf:/usr/local/nginx/conf/nginx.conf +``` + ## Base path By default, Frigate runs at the root path (`/`). However some setups require to run Frigate under a custom path prefix (e.g. `/frigate`), especially when Frigate is located behind a reverse proxy that requires path-based routing.