RTSPtoWeb: Allow option for invalid certificates for RTSPS
UniFi protect serves RTSPS streams for cameras from the controller with a certificate valid for IPv4/6 loopbacks. Trying to connect to these feeds fails with log errors similar to:
time="2022-02-05T11:19:31Z" level=info msg="Run stream" call=Run channel=0 func=StreamServerRunStreamDo module=core stream=camera.g4_doorbell_high
time="2022-02-05T11:19:31Z" level=error msg="Stream error restart stream x509: certificate is valid for 127.0.0.1, fe80::1, not <PROTECT_SERVER_IP>" call=Restart
It would be nice to allow the option to ignore the invalid certificate, in a trusted environment. For a little more context, see the discussions here.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 25 (7 by maintainers)
Commits related to this issue
- Add support for passing extra data in the stream channel Add API call to support passing extra data in the stream channel. Issue https://github.com/allenporter/stream-addons/issues/32 Issue https://... — committed to allenporter/rtsp-to-webrtc-client by allenporter 2 years ago
- Add support for passing extra data in the stream channel Add API call to support passing extra data in the stream channel. Issue https://github.com/allenporter/stream-addons/issues/32 Issue https://... — committed to allenporter/rtsp-to-webrtc-client by allenporter 2 years ago
- Add support for passing extra data in the stream channel (#49) Add API call to support passing extra data in the stream channel. Issue https://github.com/allenporter/stream-addons/issues/32 Issue... — committed to allenporter/rtsp-to-webrtc-client by allenporter 2 years ago
Nice, thanks for adding this. I think we need to “wire up” to test this in the home assistant add-on, unless one of you has a standalone instance of the server to try this out with.
try
https://github.com/deepch/RTSPtoWeb/blob/efeaa180ddb82d870585360d69f1458919eb763a/config.json#L27