-
-
Notifications
You must be signed in to change notification settings - Fork 141
Description
Hello,
I've been encountering some issues while running this program. Assuming its user error, I would love to help with the docs - this project is very interesting.
Basically, I have followed the instructions for running the application, and can't get the actual seeing the stream part to work (as in, loading video from the browser).
Websockets appear to be working.

I get the expected 'candidate success' in the browser.
There are no errors in the web browser console, and no errors in the application logs either.
The counter for the number of connected users appears to be accurate as well - when I open the page on a new browser, the counter increases.
OBS appears to be working as well:
lightspeed-ingest | 18:24:19 [ INFO] Hashes match!
lightspeed-ingest | 18:24:19 [ INFO] Client connected!
lightspeed-ingest | 18:24:19 [ INFO] Protocol Version: 0.9
lightspeed-ingest | 18:24:19 [ INFO] Vendor Name: OBS Studio
lightspeed-ingest | 18:24:19 [ INFO] Vendor Version: 27.0.0
lightspeed-ingest | 18:24:19 [ INFO] Video Codec: H264
lightspeed-ingest | 18:24:19 [ INFO] Video Height: 720
lightspeed-ingest | 18:24:19 [ INFO] Video Width: 1280
lightspeed-ingest | 18:24:19 [ INFO] Audio Codec: OPUS
I can record video and stream to twitch fine using the same OBS setup.
Its running on an EC2 instance, with what I understand to be an open enough set of firewall options.
One clue that I have is sometimes, I get the 'no_connections' info message on the websocket data before it closes:

When this happens, it closes and attempts to reopen the websocket, giving the following log in the console:
could not read message: websocket: close 1001 (going away)
could not read message: read tcp XX.XX.XX.XXX:8080->XX.XX.XXX.XX:27559: use of closed network connection
However, I do not get this all the time, only depending on the settings/environment (for example, doesn't happen in docker, but video still doesn't load).
Things I have tried
Following the firewall instructions from here: #41 (comment)
Streaming from OBS to an ssh-tunneled localhost port, as well as the port on the public IP of the VPS (ingest log suggests it works with both)
Connected to the website on ssh-tunneled localhost port, as well as the port on the public IP of the VPS.
Tested on Firefox and Chrome.
Tested on different IP address from where I'm streaming OBS from.
Tested on docker (docker compose) and when built and run from source
Tested WEBSOCKET_HOST of VPS' public ip, local IP, 172.17.0.1 (for docker), and localhost
Clicking the play button in the bottom left
I stopped just short of running the debugger on the webrtc code. Do you have any other suggestions or ideas for what I might be able to try, or where to go from here?
