Changelog: Upcoming change - TLS version requirement

From November 15th, 2026, RTMS will require TLS 1.2 or TLS 1.3 on all connections. Any connection using an older TLS version will be rejected, causing your connection to the RTMS server to fail.

What you need to do: Before November 15th, verify that your application’s server is configured to use TLS 1.2 or TLS 1.3.

To check your current version, run the following command against your RTMS endpoint:

openssl s_client -connect <rtms-host>:<port> 2>&1 | grep "Protocol"

The output should show TLSv1.2 or TLSv1.3. If it shows an older version, review the TLS settings in your:

  • WebSocket/TLS library (e.g., if using the Node.js ws library, set minVersion:'TLSv1.2' in your connection options)
  • Runtime environment (ensure your underlying SSL/TLS library support TLS 1.2+)
  • Network infrastructure (proxies, load balancers, or API gateways that may be downgrading TLS)

The supported cyphers for each version are listed below:
TLS1.2 cypher list:

  • ECDHE-RSA-AES256-GCM-SHA384
  • DHE-RSA-AES256-GCM-SHA384
  • ECDHE-RSA-CHACHA20-POLY1305
  • DHE-RSA-CHACHA20-POLY1305
  • ECDHE-RSA-AES128-GCM-SHA256
  • DHE-RSA-AES128-GCM-SHA256

TLS1.3 cypher list:

  • TLS_AES_256_GCM_SHA384
  • TLS_AES_128_GCM_SHA256
  • TLS_CHACHA20_POLY1305_SHA256