search

GRVYDEV / Project-Lightspeed

A self contained OBS -> FTL -> WebRTC live streaming server. Comprised of 3 parts once configured anyone can achieve sub-second OBS to the browser livestreaming
MIT License
3.64k stars 138 forks source link

Firefox and Edge Problems #39

Open HerrFlux opened 3 years ago

HerrFlux commented 3 years ago

Hey, does anyone have Problems with Playback in Firefox and Microsoft Edge? The problem appears for me in the Docker-compose installation and with the shell script. Currently, I am running the Docker Compose version.

With firefox, I get some really weird problems. In a Windows machine with version 72.0.1 installed the stream and website run just fine. When I try to run this on an Ubuntu Machine with the Firefox version 86.0 installed I can't load the stream it just trying to reconnect to the Websocket. In the Browser console it shows the error "the connection to ws://my_ip_adresse:8080/websocket was interrupted, while the page was being loaded." and "Socket encountered an error". Closing Socket.

In the container logs, it shows the message "lightspeed-webrtc | could not set remote description: unable to start track, codec is not supported by remote"

In Microsoft Edge, the page isn't working at all. In the console it shows"SCRIPT65536: The Argument isn't optional." pointed on line 260 in http://url/static/node-modules/react-dom/cjs/react-dom.production.min.js. Docker logs: lightspeed-react | my_ip_adresse - - [22/Mar/2021:08:14:23 +0000] "GET /static/js/2.6b14339e.chunk.js.map HTTP/1.1" 200 452018 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763" "-"

Lunaphied commented 2 years ago

I've noticed an issue like this as well. Specifically I had the stream completely stop working on a remote set of systems (both Windows 10 and Debian); the symptoms seems to be the same. Strangely there are log entries that talk about different codecs than are actually being used. I need to do more detailed analysis on the problem to determine specifically what is happening.

Gremious commented 1 year ago

This might not be strictly related, but I had similar issues on Firefox too, so leaving this for anyone stumbling:

Make sure that media.peerconnection.enabled is true in about:config. It's true by default, but extension can change it - the no WebRTC extension is pretty popular and can trip people up.

geogreen-dev commented 2 months ago

Bumping this issue. I have everything working flawlessly with Chrome but when trying to view the stream with Firefox (librewolf) nothing happens. From the webrtc logs I can see this is logged constantly: could not set remote description: unable to start track, codec is not supported by remote

And in the browser itself I can see 

Connected to websocket [SocketContext.jsx:80:14](http://192.168.1.69:8885/static/js/context/SocketContext.jsx)
Offer [App.js:83:18](http://192.168.1.69:8885/static/js/App.js)
Candidate 3 [App.js:101:18](http://192.168.1.69:8885/static/js/App.js)
Candidate success [App.js:55:14](http://192.168.1.69:8885/static/js/App.js)
Socket is closed. Reconnect will be attempted in 0.25 second. [SocketContext.jsx:85:14](http://192.168.1.69:8885/static/js/context/SocketContext.jsx)
Candidate success 2 [App.js:55:14](http://192.168.1.69:8885/static/js/App.js)
Connected to websocket [SocketContext.jsx:80:14](http://192.168.1.69:8885/static/js/context/SocketContext.jsx)
Offer [App.js:83:18](http://192.168.1.69:8885/static/js/App.js)
Candidate [App.js:101:18](http://192.168.1.69:8885/static/js/App.js)
Socket is closed. Reconnect will be attempted in 0.5 second.

btw I should note that the latest remote image doesn't include the --ice-servers arg so I had to build locally to get webrtc to even start.