rtmps not working behind NAT - undetailed exception in RTMPMinaIoHandler

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start red5 behind NAT. public_ip2:443 is configured to redirect requests to 
private_ip2:443. 
2. red5.properties is configured with private_ip2 and port 443 in RTMPS 
configuration so that it can be called from external servers. 
3. The server certificate in keystore is issued by a trusted CA present in the 
browser. The CN is public_ip2_server_name, which resolves to public_ip2 by the 
DNS.
4. Flash client (downloaded from public_ip1) points to red5 in public_ip2 and 
port 443. 

What is the expected output? What do you see instead?
I would expect the connection to be established. In red5.log and error.log I 
see very few details. Something is failing in the handshake but no details are 
reported even with logback in DEBUG. What can be done to solve this issue?

2013-12-23 14:14:00,148 [NioProcessor-18] DEBUG 
o.r.server.net.rtmp.RTMPConnection - startWaitForHandshake - Z4VAXN6JWZUSK
2013-12-23 14:14:00,175 [NioProcessor-18] WARN  
o.r.s.net.rtmp.RTMPMinaIoHandler - Exception caught on session: 1
2013-12-23 14:14:00,177 [NioProcessor-18] WARN  
o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 1
2013-12-23 14:14:00,177 [NioProcessor-18] DEBUG 
o.r.s.net.rtmp.RTMPMinaIoHandler - Forcing close on session: 1 id: Z4VAXN6JWZUSK
(...)

What version of the product are you using? On what operating system?
red5-server-1.0.2-RC1-r4709 on ubuntu

Original issue reported on code.google.com by vtor...@gmail.com on 23 Dec 2013 at 2:19

[GoogleCodeExporter]

I am also facing the problem, When i try to connect with rtmps, it is showing 
the following error in console.

[WARN] [Red5_Scheduler_Worker-2] org.red5.server.net.rtmp.RTMPConnection - 
Closing RTMPMinaConnection from 127.0.0.1 : 50433 to null (in: 283 out 598 ), 
with id 17726622 due to long handshake

Original comment by mscbalak...@gmail.com on 26 Dec 2013 at 10:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have fully checked in different environments and rtmps in 
red5-server-1.0.2-RC1-r4709 works perfectly behind NAT. The reported problem 
was caused by an incorrect keystore content. However, there was no enough 
detail in the log.

Original comment by vtor...@gmail.com on 14 Jan 2014 at 1:52

[GoogleCodeExporter]

Hi vtor, you said red5-server-1.0.2-RC1-r4709 works perfectly behind NAT, is it 
just works or need something to be configured? I'm facing similar problem using 
red5 1.0.1, i installed both on CentOS and Ubuntu.

Original comment by wi...@mitosis.my on 5 Mar 2014 at 2:25

[GoogleCodeExporter]

Issue was caused by incorrect keystore data

Original comment by mondain on 18 Apr 2014 at 2:31

• Changed state: Invalid