[Config Support]: Why my WebRTC doesn't work? #21531
-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The issue is that you haven't configured the live stream mapping between go2rtc streams and your camera.(1) Your go2rtc streams are named For the best experience, you should set the stream name under Option 1: Rename your go2rtc streams to match the camera name go2rtc:
streams:
tp_link: # Match camera name
- "ffmpeg:rtsp://admin:@192.168.xx.xx:554/stream1#video=copy#audio=aac"
- "ffmpeg:tp_link#audio=opus"
tp_link_sub:
- "ffmpeg:rtsp://admin:@192.168.xx.xx:554/stream2#video=copy#audio=aac"
- "ffmpeg:tp_link_sub#audio=opus"Option 2: Explicitly configure the live streams mapping cameras:
tp_link:
# ... existing config ...
live:
streams:
Main Stream: tp_link_main
Sub Stream: tp_link_subAdditionally, since you're accessing Frigate through nginx on a non-standard port (8443), you may need to configure WebRTC candidates properly for external access.(1) For external access over the internet, you need to set up your router to forward port 8555 to port 8555 on the Frigate device for both TCP and UDP.(1) You might also want to add a filter to your WebRTC candidates configuration to prevent connection attempts to internal Docker IPs:(2)(3) go2rtc:
webrtc:
candidates:
- 192.168.1.3:8555
- stun:8555
filters:
candidates: []📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.


The issue is that you haven't configured the live stream mapping between go2rtc streams and your camera.(1) Your go2rtc streams are named
tp_link_mainandtp_link_sub, but your camera is namedtp_link.(1)For the best experience, you should set the stream name under
go2rtcto match the name of your camera so that Frigate will automatically map it.(1) Alternatively, you need to explicitly configure thelivesection to map your go2rtc streams to the camera.(1)Option 1: Rename your go2rtc streams to match the camera name