RTSP Stream Not Working? 9 Common Problems & Fixes
Table of Contents
- Connection Refused / Timeout
- Authentication Failed (401 Unauthorized)
- Black Screen or No Video
- Private IP Address (Local Network Only)
- Firewall Blocking the RTSP Port
- Wrong RTSP URL Format
- Camera Doesn't Support Public RTSP Access
- Unsupported Codec (H.265+ or MJPEG)
- ISP Blocks or Throttles RTSP Traffic
๐ด 1. Connection Refused / Timeout
Cause: The camera IP address is unreachable, the RTSP port is closed, or the camera is offline.
Fix:
- Verify the camera is powered on and connected to the network
- Ping the camera IP from your computer โ if unreachable, check network cables and router
- Check if the RTSP port (default
554) is open:telnet camera-ip 554 - If behind a router, make sure port forwarding is set up correctly (see our DDNS guide)
- Some cameras use non-standard ports โ check your camera manual
๐ด 2. Authentication Failed (401 Unauthorized)
Cause: Wrong username or password in the RTSP URL.
Fix:
- Double-check the camera admin credentials
- RTSP URL format:
rtsp://username:password@camera-ip:554/stream1 - If your password contains special characters like
@,:,/, URL-encode them:%40for@,%3Afor: - Some cameras have a separate RTSP user (different from the web admin) โ enable it in camera settings
๐ด 3. Black Screen or No Video
Cause: Codec not supported by the player, or the stream is in a format your browser can't decode.
Fix:
- Try both MSE and WebRTC players on RTSP.cam โ different browsers support different codecs
- Make sure the camera is streaming (check its web interface)
- Some cameras send a blank stream when no motion is detected โ adjust motion detection settings
- Try a different RTSP URL path โ common ones:
/Streaming/Channels/101(Hikvision),/cam/realmonitor?channel=1&subtype=0(Dahua)
๐ด 4. Private IP Address (Local Network Only)
Cause: You entered a private (internal) IP like 192.168.x.x, 10.x.x.x, or 172.16-31.x.x. These addresses only work within your local network.
Fix:
- You need the public IP address of your router, not the camera's internal IP
- Set up DDNS (Dynamic DNS) so your router gets a hostname that always works
- Configure port forwarding on your router to forward RTSP port (554) to the camera
- See our full DDNS & Port Forwarding guide for step-by-step instructions
๐ด 5. Firewall Blocking the RTSP Port
Cause: A firewall (on the router, camera, or ISP level) is blocking the RTSP port.
Fix:
- Check your router's firewall settings โ make sure port 554 (or your custom RTSP port) is open
- Some routers have "SPI firewall" that blocks non-HTTP traffic โ disable or add an exception
- Check the camera's own firewall/access control settings
- Try a different RTSP port (e.g., 8554) and forward that instead โ some ISPs block port 554
๐ด 6. Wrong RTSP URL Format
Cause: The RTSP path after the IP address is incorrect. Each camera brand uses a different URL structure.
Fix: Use the correct RTSP URL for your camera brand:
Hikvision: rtsp://user:pass@ip:554/Streaming/Channels/101 Dahua: rtsp://user:pass@ip:554/cam/realmonitor?channel=1&subtype=0 Axis: rtsp://user:pass@ip:554/axis-media/media.amp Uniview: rtsp://user:pass@ip:554/unicast/c4s1/live RTSP: rtsp://user:pass@ip:554/stream1
For more camera brands, check our guide to finding your RTSP URL.
๐ด 7. Camera Doesn't Support Public RTSP Access
Cause: Some consumer cameras don't expose RTSP externally by default, or require enabling it in settings.
Fix:
- Log into your camera's web interface and look for RTSP settings
- Enable "RTSP Service" or "RTSP Authentication" (may be under Network โ Advanced โ RTSP)
- Some cameras (like Reolink, Annke) require creating a separate RTSP user account
- Consider using VPN (WireGuard/OpenVPN) instead of exposing RTSP directly to the internet
๐ด 8. Unsupported Codec (H.265+ or MJPEG)
Cause: The camera is using H.265+ (a proprietary extension of H.265), MJPEG, or another non-standard codec.
Fix:
- In your camera settings, switch the stream to H.264 or standard H.265
- RTSP.cam supports H.264, H.265 (HEVC), and AV1
- If your camera has multiple streams (main + sub), try the sub-stream which often uses H.264 by default
- MJPEG is not supported through RTSP โ use the camera's HTTP snapshot URL instead
๐ด 9. ISP Blocks or Throttles RTSP Traffic
Cause: Some ISPs block or throttle non-standard ports and streaming protocols.
Fix:
- Try using a non-standard RTSP port (e.g., forward port 8554 instead of 554)
- Check your upload bandwidth โ RTSP streams need at least 2-4 Mbps for HD video
- If your ISP uses CGNAT (Carrier-Grade NAT), you cannot port forward โ request a public IP or use a VPN/tunnel
- Consider using RTSP over HTTPS or tunneling through a VPN
๐ก Still stuck? Try testing your RTSP stream on RTSP.cam โ it will show you detailed error messages and stream diagnostics. If you see a "connection refused" error, the issue is usually on the network/router side. If the video loads but shows nothing, it's likely a codec issue.