forked from arut/nginx-rtmp-module
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Unable to restream to Telegram #350
Comments
same problem with Telegram when push via stunnel, no video, but data sents to Telegram |
@sergey-dryabzhinsky |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are able to use the NGINX RTMP module to re-stream to many public streaming services, using the
push
directive. This directive only allow pushing to RTMP targets and does not support RTMPS. If we use the NGINX SSL stream module to provide the SSL support we can easily work around this limitation (this approach as well as using Stunnel is quite prevalent). This workaround works for many platforms but fails for Telegram.We have tested using the following configuration using OBS as the source client:
There are no errors logged in the NGINX logs, in fact the logs show that the connection is established normally and the stream sent. On the Telegram application, no video is received. Note that when using FFMPEG or OBS to stream directly to Telegram, it works correctly.
The text was updated successfully, but these errors were encountered: