![]() Double-check the documentation for your encoder. If you're still having trouble, then your encoder may not support RTMPS. If you see an error like 'failed to connect to server – connection timed out', then try the following:įollow the steps in ' Set the server URL' to make sure that the server URL is correct.īoth the protocol and the server should be rtmp s, not just rtmp. Or, if your encoder lets you specify the port number in the configuration options, use 443 there. Here's an example, but you'll need to update the server URL that you get from Live Control Room: Æðelstan I completely agree with you but that the thing i am unable to figure out.What ideally should happen is that RTMP is packaged inside TCP which is in turn packaged inside IPv4.Hence the size of RTMP packet must be included in the TOTAL LENGTH FIELD of IPv4 packet. ![]() ![]() If the URL looks correct but you still get an SSL error, try specifying the port 443 in the URL. Both the protocol and the server should be rtmp s, not just rtmp. If you see an error like 'the RTMP server sent an invalid SSL certificate', try the following:ġ – Make sure that the server URL is correctįollow the steps in ' Set the server URL' to make sure that the server URL is correct. Copy your YouTube stream key from Live Control Room and paste it into your encoder.Under 'Stream settings', in the Stream URL field click the lock icon to reveal the RTMPS URL.Click the Stream tab or schedule a new stream.Note that it will still show you the ordinary RTMP URL by default, so make sure that you get the RTMPS URL instead. You can get the RTMPS URL from Live Control Room. It is RTMP over a Transport Layer Security (TLS/SSL) connection and provides. If your encoder doesn't have a YouTube RTMPS preset, go to 'Set the server URL'. You can stream to YouTube Live with RTMPS, a secure extension to the popular RTMP streaming video protocol. You may need to enter your stream key from Live Control Room too. If you see a YouTube RTMPS preset, select it. Which surprisingly gone in the RTMP payload view: As you can see, the C3 byte disappeared in the RTMP view. Heres the packet in Wireshark: The C3 byte makes the RTMP longer than expected. Update your encoder to the newest version and check for a built-in setting for YouTube RTMPS. In one of the captured packets, the TCP payload length is longer than expected. Make sure that your encoder supports RTMPS and that you know the basics of live streaming on YouTube. It is RTMP over a Transport Layer Security (TLS/SSL) connection and provides encryption. You can stream to YouTube Live with RTMPS, a secure extension to the popular RTMP streaming video protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |