Port 1935: RTMP (Flash/OBS streaming)

RTMP (Flash/OBS streaming)

Port 1935 — RTMP (Real-Time Messaging Protocol), originally Adobe Flash. Today it is the standard for streaming ingest: OBS Studio, Twitch, YouTube Live, Facebook Live. Flash deprecated in 2020, but RTMP ingest remains (transcoded to HLS/DASH server-side).

RTMP is plaintext (no TLS). Use RTMPS (TCP 443) for security. Stream keys are secrets — leak = stream hijack. Rotate keys after each session.

Check port online →

Enterno.io Ping + Port checker tests TCP reachability of any port from 3 regions (Moscow / Frankfurt / Virginia).

RTMP, or Real-Time Messaging Protocol, is primarily used for streaming audio, video, and data over the Internet. Originally developed by Adobe for Flash, it has evolved into a widely adopted protocol for live streaming applications.

Port 1935 (TCP) serves as the default port for RTMP, facilitating seamless interactions between streaming applications and content delivery networks (CDNs). Here are some common applications that utilize RTMP:

• OBS Studio: A popular open-source software for video recording and live streaming, OBS Studio uses RTMP to send video and audio feeds to platforms like Twitch and YouTube Live.
• Twitch: This leading gaming platform employs RTMP for stream ingestion, allowing gamers and content creators to broadcast their gameplay live to millions.
• YouTube Live: YouTube's live streaming service leverages RTMP for real-time video transmission, ensuring minimal latency for viewers.
• Facebook Live: Using RTMP, Facebook Live enables users to share live video content directly to their profiles or pages.

Despite its origins with Flash, RTMP remains a cornerstone for many contemporary streaming solutions due to its low latency and ability to handle high-quality video and audio.

While Port 1935 is essential for RTMP streaming, it also presents several security considerations that users and organizations must address to protect their streaming infrastructure.

Here are key security practices to consider:

• Firewall Configuration: Ensure that your firewall is properly configured to allow traffic on Port 1935 only from trusted IP addresses. This minimizes the risk of unauthorized access.
• Use RTMPS: Whenever possible, use RTMPS (RTMP Secure) instead of RTMP. RTMPS encrypts the data being transmitted, protecting it from eavesdropping and man-in-the-middle attacks.
• Access Control: Implement strong authentication mechanisms to restrict access to your streaming server. This can include using tokens or secure login credentials.
• Regular Updates: Keep your streaming software and server operating systems updated to protect against known vulnerabilities that could be exploited by attackers.

By following these security guidelines, you can significantly reduce the risks associated with streaming over Port 1935 while ensuring a safe and reliable streaming experience.

Configuring RTMP using Port 1935 is vital for setting up a live streaming service. Below are practical examples of commands and configurations you can use with popular streaming software and servers.

1. Configuring OBS Studio:

To set up OBS Studio to stream to a platform like Twitch, follow these steps:

• Open OBS Studio and navigate to Settings.
• Select Stream from the left menu.
• Choose Twitch as the service.
• Set the Server to the closest Twitch server.
• In the Stream Key field, enter your Twitch stream key.
• Click OK to save the settings.

2. Using FFmpeg to Push RTMP Stream:

If you're using FFmpeg to push a stream to an RTMP server, use the following command:

Replace input.mp4 with your video file and rtmp://yourserver.com/live/stream with your RTMP server URL.

3. Nginx with RTMP Module:

If you're setting up your own RTMP server using Nginx, you can configure it as follows:

After saving your configuration, restart Nginx to apply the changes. This will enable RTMP streaming on Port 1935.

These examples provide a foundational understanding of how to set up and configure RTMP streaming effectively using Port 1935.