Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stream died #8

Closed
stan69b opened this issue Aug 15, 2020 · 6 comments
Closed

Stream died #8

stan69b opened this issue Aug 15, 2020 · 6 comments
Labels
question Further information is requested

Comments

@stan69b
Copy link

stan69b commented Aug 15, 2020

Hello, i've been using this lib for a couple of month and all was working perfectly, but recently, i've been recieving this error message server side, even though i haven't updated my client or server in a while.

Do you happend to have an idea of what the problem might be ?

http://www.umbitchoise.com/live

i'm NOT using ssl so http:// and ws:// only.

(i'm using your code from the readme, without any changes apart from the rtsp stream which works as i tester id with vlc)

18:18:55 18|UMB - Camera | [rtsp-relay] New WebSocket Connection
18:18:55 18|UMB - Camera | [rtsp-relay] Creating brand new stream
18:19:06 18|UMB - Camera | [rtsp-relay] Stream died - will recreate when the next client connects

Thanks for any tips you have :)

Screenshot 2020-08-15 at 18 53 25

@k-yle
Copy link
Owner

k-yle commented Aug 16, 2020

Hi, I've realised that not all errors are logged, even if verbose: true. I've published v1.0.6 which will now show additional logging in verbose mode.

let me know if you see any new error messages in v1.0.6; as they will provide more insight into why the stream died.

@k-yle k-yle added the question Further information is requested label Aug 16, 2020
@stan69b
Copy link
Author

stan69b commented Aug 16, 2020

Thanks for the update.
if i'm not mistaken, you added the this.stream.on('error' ... but it seems i'm not getting an error server side. most likely the clients exits the socket for some reason :(

I'm stating to believe that browsers exit the socket if it is not secured but it's just a guess :/
Thanks anyway for the added logs, it did help me identify that the bug does not seem to be coming from your lib ;)

@stan69b
Copy link
Author

stan69b commented May 13, 2021

Little update, we were on a very slow network for this installation and probably unstable. We switched to a fiber optics connection recently and after setting up the camera again, everything juste started working again. I cannot explain what really happened, but it was clearly not related to your tool :)

I'm closing the issue now as it is not relevant to your program. Thanks again for your help and your update to help me debug my setup.

@stan69b stan69b closed this as completed May 13, 2021
@ironwaka
Copy link

Hello, I have encountered a similar problem with you recently. Have you found a solution? Thank you for your prompt!

@phiberber
Copy link

Been having the same issue here, it was working but now it isn't

@phiberber
Copy link

phiberber commented Feb 4, 2022

The problem with me: I was using rtmp-rtsp-stream-client-java to send the camera information from a device to the server, but I was disabling its audio as the audio is useless in my situation. Seems that when the Android Microphone permission is not given, it'll encode the audio differently, so rtsp-relay will not be able to display it. Not really sure why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants