0

I am attempting to connect to my Red5 server with an RTMP client through an SSL socket. Based on Paul Gregoire's blog post about Red5 and RTMPS, these are the steps that I took to set up a new Red5 RTMPS server:

  1. Download and install a fresh version of Red5 from the Red5 1.0 download page
  2. Uncomment the RTMPS section of the {red5 dir}/conf/red5-core.xml file. This section contains the same settings that Paul Gregoire mentions in step 8 of his blog post.
  3. Leave the {red5 dir}/conf/red5.properties unchanged; the RTMPS port is set to the default 8443 and the server SSL keystore is left as the one packaged with Red5

I then proceed to start up the Red5 server with the JVM argument "-Djavax.net.debug=ssl" so that SSL debug information will be displayed in the console.

As a simple test, I try connecting to the server with node.js by using the tls library:

tls.connect(8443, 'localhost', null);  // tls.connect(port, host, callback);

The first thing I notice in the server console is line 1106:

[DEBUG] [pool-11-thread-1] org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Handshake init too small, buffering. remaining: 338

My first thought is that the RTMP handshake is unable to be decoded by the server because the server is skipping over the SSL handshake that the client is trying to initiate. By further combing the server console, I see that the SSL handshake never happens despite the client connecting through an SSL socket. Here is the full server console output of the result of the node.js client calling the aforementioned line.

What am I doing wrong when trying to connect to the server through SSL and how should Red5 be set up to use RTMPS?

mburke13
  • 350
  • 2
  • 6
  • 22
  • 1
    I faced a similar issue a few years ago... did you try to use a certified certificate? – fmodos Jul 03 '13 at 03:32
  • @fmodos I have no tried that yet. I guess that would be the next logical step, but I assumed that an unsigned certificate would programatically work the same way. I'll try it out and post back with the results. – mburke13 Jul 03 '13 at 21:08
  • I could never make it work in older versions without a signed certificate :/ – fmodos Jul 04 '13 at 23:31

0 Answers0