AlexxIT
MJPEG no longer works since updating to WebRTC 3.6.1
I was able to integrate my USB webcam, which is provided as an HTTP stream via Netcam Studio, without any problems up to WebRTC version 3.6.0. Now I get the following error: mse:streams: Get "http://xxx.xxx.xxx.xxx:8100/Mjpeg/0" net/http: HTTP/1.x transport connection broken: bad Content-Length"-1"
Hey @MarkusHempel Sorry I cant be more help, but I came here to report a bug, which might be related due to 3.6.0 >> 3.6.1 change. For some reason my UniFI protect streams in 3.6.1 constantly are buffering using the rtsps streams, move it back to 3.6.0 and everything works again. I thought it may have been some firewall changes I had made at the same time approx, but after reverting those changes, the only fix was downgrade to 3.6.0. To the dev team, if there is anything I can do to troubleshoot/test or help let me know.
@Rattleheadie if Unifi doesn't use MJPEG then you should open a separate issue.
I don't think this is related to the v3.6.0 update. Your camera response with bad content-length. Go2rtc can't do anything with this.
