Dear Christian,
As per my understanding SSL certificate is required for frontend
nginx/Apache webserver.
If we use RTMPS then we have to deal with keystone and truststore, right?
What if I use simple RTMP which tunnel through https, which settings should
I have to change for that?
And another
Dear Hemant,
In Darshit's case, [if] it is Nginx https + OM http. In such a case, the SSL will be terminated at Nginx. Only HTTP requests will be sent to Tomcat.
This is exactly correct. This is independent of nginx. Could also be
apache, lighttpd, haproxy or any other reverse proxy with
I missed an IF in the sentence below.
Following scenario: In Darshit's case, IF it is Nginx https + OM http.
-Original Message-
From: Coscend@OM
Sent: Tuesday, July 24, 2018 1:48 AM
To: 'user@openmeetings.apache.org'
Subject: RE: How to run openmeeting on RTMPS with nginx in frontend
Dear Christian,
Could you help us understand a little more about the following scenario?
In Darshit's case, it is Nginx https + OM http. In such a case, the SSL will
be terminated at Nginx. Only HTTP requests will be sent to Tomcat. In
addition to Admin ->Config (flash.secure = true,
Dear Darshit,
you need to enable the RTMPS in /conf/jee-container.xml.
It is there already but commented out.
Also make sure that the keystore and truststore are correctly labeled (I
had problems with them in the default configuration) and have the
correct passwords.
Cheers
Christian
Am
Hi,
I have deployed openmeeting(4.0.4) on a Linux server, having nginx in
frontend which redirects all https requests to openmeeting instance running
on localhost. On server, I want to keep open port number 443 only(all other
ports will be close), but if I do that audio is not working.
I look
