Streaming: Facebook moves live videos completely to RTMPS
Facebook today announced that all live video uploads will be required to use RTMPS (RTMP over a TLS/SSL connection) by May 1, 2019. Publishers need to shift from RTMP (insecure) to RTMPS (RTMP over a TLS/SSL connection).
Facebook today announced that all live video uploads will be required to use RTMPS (RTMP over a TLS/SSL connection) by May 1, 2019. Publishers need to shift from RTMP (insecure) to RTMPS (RTMP over a TLS/SSL connection).
Facebook says integrations using RTMP will not continue to work after the deadline. Only integrations using RTMPS for live videos will continue to work, as they provide a greater level of security for the video content.
RTMP vs RTMPS
RTMP means Real-Time Messaging Protocol. RTMP works on top of and uses TCP port number 1935 by default, while RTMPS goes over a TLS/SSL connection, which means the connection is encrypted.
Here how to migrate to RTMPS:
- Ensure that librtmp was compiled with OpenSSL or one of the supported alternatives.
- Once the call to the Facebook Graph API is done to create your live_video object, developers can use either the stream_url or secure_stream_url fields which will both contain the secure RTMPS URL.
Subscribe to our free weekly LinkedIn newsletter for a weekend roundup, or upgrade to our real-time updates for just $10/year. Get the latest marketing news and insights delivered straight to your inbox.