Well, it did seem to be an effect of the path: the error message
disappeared once I changed
<property name="keystoreFile" value="conf/keystore">
into
<property name="keystoreFile" value="/data/openmeetings/conf/keystore">
in red5-core.xml
This reflects the real path on my server. Some one might want to add
this to the documentation.
The situation now is like this gentleman describes:
https://issues.apache.org/jira/browse/OPENMEETINGS-500
I can't shake the feeling the documentation is missing something ...
BC
On 01/28/13 00:49, Bart Coninckx wrote:
One addition: I installed in /data/openmeetings, but I had this
reflected in the init.d script that starts OpenMeetings. I hope that
is OK?
BC
On 01/28/13 00:47, Bart Coninckx wrote:
Hi all,
been trying to get SSL rolling following the docs on
http://incubator.apache.org/openmeetings/RTMPSAndHTTPS.html
I doublechecked everything but conecting to the OM site produces a
"try 1", "try 2" etc and ends in NetConnection.Connect.Failed
The red5 console says:
[WARN] [NioProcessor-19] org.red5.server.net.rtmps.RTMPSMinaIoHandler
- Exception caught Keystore or password are null
the keystore is in "RED5_HOME"/conf and the passwords works.
While capturing the packets I see a lot on 443, so HTTPS seems OK and
jsut a fiew on 5443, so my guess is that RTMPS has a problem.
The only step I did not do in the docu was:
7. Create additional certificate as described above. Add this
certificate to the following keystores: red5/conf/keystore.screen and
red5/conf/keystore.
as it is not very clear. Do you need to create a new CSR and next a
new CRT? Because that makes no sense. Or do I need a new keystore
named keystore.screen and import the same certificates?
Thx for clarifying this,
BC
