Hi everyone!

A customer of mine recently set up an Openmeetings instance on his
server. He asked me to add SSL support to it, so I followed the steps
described on this page:

https://openmeetings.apache.org/RTMPSAndHTTPS.html

We'd like to use a self-signed certificate for testing and then move to
a regular, officially signed cert for our production environment later.
So I created a CA and a server certificate for Openmeetings with
EasyRSA. The steps to import the certificate, the certificate key and
the CA certificate into the keystore / truststore succeeded.

I then followed the steps to enable HTTPS on the web interface:
https://openmeetings.apache.org/RTMPSAndHTTPS.html#SSL_for_the_web_interface

... and restarted the red5 service.

But unfortunately Openmeetings does not respond to requests to
https://myserver:5443 while it keeps working fine on Port 5080
(http://myserver.tld:5080). The connection to the server seems to be
established, but every browser waits for a response, which it obviously
does not get. Firewall is set up properly and does not block the request.

I'm new to Openmeetings, so I'm having a hard time to investigate this
error.
What might go wrong? How can I debug this error and where do I find
helpful log files?
I had a look at the "log" directory but there aren't any error messages
logged.

It would be awesome to get some tips and advice from a long-term
Openmeetings user. :-)

Best regards,
Thomas

Reply via email to