I have no SSL test environment currently. I did not run into this issue. I did only find the corresponding code that throws your issue in the red5 sources: http://code.google.com/p/red5/source/browse/java/server/trunk/src/org/red5/server/net/rtmp/codec/RTMPProtocolDecoder.java#212
However there is no advice in the source how to resolve it. Maybe some other users have an idea that successfully run OpenMeetings via SSL, for example the people asking for the RTMPSClient feature in the Screensharing. Sebastian 2012/5/16 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > I'm currently trying to setup and test RTMPS for Screen sharing. > > I perform all steps from instruction > But still unable to get RTMPS working > Here is extended log: > > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslHandler - Session > Server[1](ssl...) processing the FINISHED state > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslHandler - Session > Server[1*](SSL) is now secured* > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslHandler - Session > Server[1](SSL) processing the FINISHED state > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslHandler - Session > Server[1]*(SSL) is now secured* > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslFilter - Session > Server[1](SSL): Processing the SSL Data > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslFilter - Session > Server[1](SSL): Message received : HeapBuffer[pos=0 lim=213 cap=1024: 17 03 > 01 00 D0 67 A1 06 4E 8C EB EB 42 D8 D7 A2...] > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslHandler - Session > Server[1](SSL) Processing the received message > [DEBUG] [NioProcessor-18] org.apache.mina.filter.ssl.SslFilter - Session > Server[1](SSL): Processing the SSL Data > [DEBUG] [NioProcessor-18] org.apache.mina.filter.codec.ProtocolCodecFilter > - Processing a MESSAGE_RECEIVED for session 1 > [DEBUG] [NioProcessor-18] > org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Start: 0 > [DEBUG] [NioProcessor-18] > org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - decodeHandshake - > rtmp: RTMP [state=connect, client-mode=false, debug=false, encrypted=false, > lastReadChannel=0, lastWriteChannel=0, readHeaders={}, writeHeaders={}, > readPacketHeaders={}, readPackets={}, writePackets={}, writeTimestamps={}, > liveTimestamps={}, readChunkSize=128, writeChunkSize=128, encoding=AMF0] > buffer: HeapBuffer[pos=0 lim=183 cap=1536: 50 4F 53 54 20 2F 6F 70 65 6E 2F > 31 20 48 54 54...] > [DEBUG] [NioProcessor-18] > org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - *Handshake init too > small, buffering. remaining: 183* > [WARN] [Red5_Scheduler_Worker-2] org.red5.server.net.rtmp.RTMPConnection - > *Closing RTMPMinaConnection from 192.168.72.100 : 64634 to null (in: 931 > out 3083 ), with id 1 due to long handshake* > > > As you can see SSL is secured (no issues) > but then I got: > "Handshake init too small, buffering. remaining: 183" > and > "Closing RTMPMinaConnection from 192.168.72.100 : 64634 to null (in: 931 > out 3083 ), with id 1 due to long handshake" > > > > I'm using self-signed certificate with fake CA (added both to the server > and client) > > client debug is: > "devRtmpConnection/registerMethods() > error NetConnection.Connect.Failed rtmps:// > 192.168.72.105:5443/openmeetings/hibernate null false " > > > Can you help me with it? > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
