-
-
Notifications
You must be signed in to change notification settings - Fork 797
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
Connection Failed when upgrading to newest version (2.5.2 - 2.5.7) #1723
Comments
Hello, I'm testing using that url with version 2.5.7 and version 2.5.1 and I receive the same error. Can you share a valid url to test? |
Hi @pedroSG94 , And it didn't work from this commit. |
Hi @pedroSG94 , Update: Thanks. |
Hello, It is maybe related with ktor. Can you test with master branch which contain an update of ktor? compile the project and use the last commit. |
No, if it is working with rtmp the parser is working correctly |
Hi @pedroSG94 , it shows connection error java.io.EOFException: Channel is already closed
|
Can you share me a valid endpoint to connect? I'm no able to connect using the old version 2.5.1 |
I was able to create my own livekit server and reproduce the problem. I will work in this and release a fix |
Thank you so much |
Hello, I'm working in this but this seem a bug in ktor using tls socket. I can fix the problem using java.io blocking api for socket like before but this could have others problems blocking the send sometimes. I'm looking the best way to do it but I'm not sure how to do it for now. |
Hi,
I use 2.5.1 and it works well, I start streaming from mobile and can see the video streaming on the website.
I want to upgrade to newer version(2.5.2 - 2.5.7) to remove the noise when streaming using rtmpStream.setTimestampMode(TimestampMode.BUFFER, TimestampMode.BUFFER);
But when I upgrade to newer version, it had errors like this, and I can't see the video streaming on the website.
'rtmps://abc-live-20-01-abcd.rtmp.livekit.cloud/x/abcdef'
My initialization:
Thanks.
The text was updated successfully, but these errors were encountered: