Known Issues - Red5 Pro Server

  • New version of Chrome/Chromium requires Eliptical Curve support in WebRTC DTLS, this is added in the 12.4 version of Red5 Pro Server
  • ABR Rate switching not working with Mixer feeding a Transcoder
  • The cluster server becomes a listener upon every shared object. That should explain why listener count always starts with 2
  • Publish Screen Share Testbed example needs these settings to be enabled on MacOS for allowing screen share onto different browsers : System Settings > Privacy & Security > Screen Recording and add/allow the browser to be used for screen share
  • Shared Object(Websocket Only) testbed example : There is no websocket or shared object testing in conjunction with WHIP/WHEP connections though same should work with WS (uncheck WHIP/WHEP on the settings page)
  • Re-publishing/ re-subscribe takes 2-3 seconds for starting the stream with the same stream name.
  • Subscribe AMF Metadata : Current implementation trims any extra spacing and just takes a single space when entered
  • Notifications for Publisher-Subscriber connect/disconnect for RTMP connections is throwing some unexpected messages
  • While RTMP connections are removed from the count of "connected clients", they are not removed from the count of "stream subscribers"
  • Shared objects testbed example does not support the special characters " and \
  • Region-specific targeting via autoscale requires the &strict=true to be enforced.
  • For server version >= 9.0.0, if you need the Orientation post-processor feature, contact us at info@red5pro.com to help get you a compatible FFmpeg library.
  • If using the Orientation Post Processor, note that the Android SDK recordings take approximately 3 times the duration of the file to convert to MP4; modify the cloudstorage-plugin.properties file, setting the max.transcode.minutes= value to allow for this timing
  • IMPORTANT: Because of different libcrypto library versions supported between CentOS and Ubuntu, if you are using CentOS or Ubuntu >=22.04 it is necessary to modify {red5pro}/conf/webrtc-plugin.properties, and change openssl.enabled=true to openssl.enabled=false

  • Some issues have been reported with WebRTC using Chrome v100 on the Mac M1 chipset, but these appear to have been resolved with macOS Monterey v12.4 and Chrome v102.
  • There are threading issues on Ubuntu 18 which may lead to OOM errors at more than 1,400 connections (Server Version 9.0.0 runs on Ubuntu 20.04 which does not exhibit the same issues)
  • For Safari < v12 (iOS < 12), iOS SDK broadcast cannot be viewed with WebRTC in Mac or iOS Safari
  • With the release of Microsoft Edge Chromium, we have dropped support for older versions of Edge
  • Some issues with some versions of Safari WebRTC <==> Firefox WebRTC
  • If you are upgrading your server/webapp from a version older than 11.0.0, please see these details on WHIP/WHEP.
  • With server >= 8.0.0, for localhost testing, it may be necessary to set force.local.ip= to your machine's IP address in conf/webrtc-plugin.properties

See the CVE page for mitigated vulnerabilities.