Skip to content
RU

Port 8554 — RTSP

Wall-mounted IP security camera with a cable, monitor below showing four blurred camera feeds
Key idea:

TCP 8554 is the most common alternate port for RTSP (the standard one is 554). MediaMTX (formerly rtsp-simple-server) and the GStreamer gst-rtsp-server examples listen on it by default, which is why stream URLs look like rtsp://localhost:8554/live or /cam1. Unlike 554, an unprivileged user can bind it. Protect streams with RTSP digest auth or RTSPS (TLS) and keep cameras off the open internet.

Below: details, example, related, FAQ.

Check your host & ports →

Details

  • RTSP is a "remote control" for media streams, not data transport (RTP uses other ports)
  • URL schema: rtsp://user:pass@192.168.1.10:8554/stream1
  • ONVIF cameras often expose 8554 for an alternate profile
  • FFmpeg, VLC, GStreamer — all speak rtsp:// URIs
  • WebRTC is pushing RTSP out of web apps, but IP cameras still run RTSP

Example

# Check stream with ffmpeg
$ ffmpeg -rtsp_transport tcp -i rtsp://admin:pass@192.168.1.10:8554/live -frames 1 test.jpg

# GStreamer play
$ gst-launch-1.0 rtspsrc location=rtsp://192.168.1.10:8554/live ! decodebin ! autovideosink

# Nmap scan
$ nmap -p 8554 --script rtsp-url-brute 192.168.1.10

Related

Advantages of Using Port 8554 for RTSP

Port 8554 serves as a widely accepted alternative to the standard RTSP port 554, offering several advantages for developers and system administrators.

  • Compatibility: Many applications, especially those based on GStreamer, default to port 8554, making it easier to integrate various streaming tools.
  • Firewall Bypass: In environments with strict firewall rules, port 8554 is often more accessible, allowing for smoother connectivity without extensive reconfiguration.
  • Test and Development: Developers frequently use port 8554 for testing purposes, enabling quick setup of RTSP servers without interfering with existing production services on port 554.
  • Support for CGNAT: Port 8554 is beneficial in Carrier-Grade NAT scenarios, where multiple users share a single public IP address, facilitating better routing and connectivity.

By leveraging these advantages, organizations can enhance their streaming capabilities while ensuring robust performance and security.

Configuring RTSP on Port 8554: Practical Examples

Configuring RTSP to operate on port 8554 can be straightforward. Below are a few practical examples using different environments and tools.

Example with GStreamer

To set up an RTSP server using GStreamer on port 8554, you can use the following command:

gst-launch-1.0 -v videotestsrc ! x264enc ! rtph264pay ! gdppay ! tcpserversink host=0.0.0.0 port=8554

This command streams a test video from the source and serves it over RTSP on port 8554.

Example with FFmpeg

For those using FFmpeg, you can create an RTSP stream on port 8554 with:

ffmpeg -re -i input.mp4 -c:v libx264 -f rtsp rtsp://localhost:8554/live.sdp

This command reads a video file and streams it to an RTSP endpoint on port 8554.

Example with VLC

To stream from VLC media player, go to:

  • Select Media > Stream.
  • Add your media file and select Stream.
  • Choose RTSP as the output format and set the port to 8554.

These examples illustrate the versatility and ease of configuring RTSP streaming on port 8554 across various platforms.

Security Considerations for RTSP on Port 8554

When using port 8554 for RTSP streaming, security should be a top priority to protect sensitive video data. Here are key considerations and best practices:

  • Authentication: Implementing digest authentication is crucial to ensure that only authorized users can access the stream. This can be configured in your RTSP server settings.
  • Encryption: Utilize RTSPS (RTSP over TLS) for encrypting the data stream. This ensures that all transmitted video content is secure from eavesdropping.
  • Access Control: Restrict access to your RTSP server by configuring IP whitelisting or using VPNs. This minimizes the risk of unauthorized access.
  • Regular Updates: Keep your RTSP server software up to date to protect against vulnerabilities. Regularly check for patches and updates from the software provider.
  • Monitoring: Implement logging and monitoring to track access attempts and potential security breaches. Tools like fail2ban can help in automatically blocking suspicious IP addresses.

By adhering to these security measures, organizations can significantly mitigate risks associated with RTSP streaming over port 8554, ensuring a secure and reliable streaming experience.

Learn more

Sources

Frequently Asked Questions

Why 8554 specifically?

Often — a user-space alternative to privileged 554. Standalone servers without root use 8554 / 8888 / 10554.

RTSP security?

Digest auth + IP whitelist. Real security — TLS tunnel (stunnel / nginx-rtmp-module) or WebRTC + SRTP.

Replace RTSP?

Browser — WebRTC or HLS. IP cameras and professional video — RTSP for another 5+ years.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.