Latest instructions for 4.0.10 can be found here https://om.alteametasoft.com/openmeetings/docs/RTMPSAndHTTPS.html
Yes it is possible Please search the archives On Fri, 10 Apr 2020 at 19:03, ratatouille <ratatoui...@bitclusive.de> wrote: > Hello! > > apache-openmeetings-4.0.10.tar.gz > > Can I use a letsencrypt keyfile to create/import to keystore? > > Andreas > > > Maxim Solodovnik <solomax...@gmail.com> schrieb am 10.04.20 um 18:38:20 > Uhr: > > > What version are you working with? > > > > On Fri, 10 Apr 2020 at 18:36, ratatouille <ratatoui...@bitclusive.de> > wrote: > > > > > Hello! > > > > > > According to > > > > https://svn.apache.org/repos/asf/openmeetings/site/trunk/RTMPSAndHTTPS.html > > > I modifed > > > > > > 1. Edit red5/conf/jee-container.xml file: > > > Comment Tomcat without SSL enabled section > > > UNComment Tomcat with SSL enabled section > > > 2. Edit red5/webapps/openmeetings/public/config.xml and set > > > > > > There is no $om/webapps/openmeetings/public/config.xml > > > > > > Native RTMPS > > > 2. Edit red5/conf/red5-core.xml file: > > > UNComment RTMPS section > > > 3. Edit red5/webapps/openmeetings/public/config.xml and set > > > > > > Again, there is no $om/webapps/openmeetings/public/config.xml > > > > > > OM starts but I get an error > > > > > > Apr 10, 2020 1:21:05 PM org.apache.catalina.util.LifecycleBase > > > handleSubClassException > > > SCHWERWIEGEND: Failed to initialize component > > > [Connector[org.apache.coyote.http11.Http11Nio2Protocol-5443]] > > > org.apache.catalina.LifecycleException: Protocol handler initialization > > > failed > > > > > > Caused by: java.lang.IllegalArgumentException: > > > /home/andreas/om/conf/keystore.jks (Datei oder Verzeichnis nicht > gefunden) > > > > > > Is it mandatory to set up a keystore first? > > > > > > -rw-r----- 1 andreas users 1670 25. Feb 2014 access.properties > > > -rw-r----- 1 andreas users 10476 24. Okt 2014 catalina.policy > > > -rw-r----- 1 andreas users 1656 26. Jul 2016 context.xml > > > -rw-r----- 1 andreas users 14172 25. Feb 2014 ehcache.xml > > > -rw-r----- 1 andreas users 6188 10. Apr 13:17 jee-container.xml > > > -rw-r----- 1 root root 6218 10. Apr 12:59 jee-container.xml.orig > > > -rw-r----- 1 andreas users 1364 25. Feb 2014 keystore.jmx > > > -rw-r----- 1 andreas users 920 5. Feb 2016 logback.xml > > > -rw-r----- 1 andreas users 613 30. Jan 2016 no-jee-container.xml > > > -rw-r----- 1 andreas users 1346 25. Feb 2014 password.properties > > > -rw-r----- 1 andreas users 449 25. Feb 2014 realm.properties > > > -rw-r----- 1 andreas users 10968 20. Apr 2019 red5-common.xml > > > -rw-r----- 1 andreas users 14383 10. Apr 13:20 red5-core.xml > > > -rw-r----- 1 root root 14379 10. Apr 13:08 red5-core.xml.orig > > > -rw-r----- 1 andreas users 55 25. Feb 2014 red5.globals > > > -rw-r----- 1 andreas users 12790 23. Jan 2016 red5.policy > > > -rw-r----- 1 andreas users 5035 13. Dez 2018 red5.properties > > > -rw-r----- 1 andreas users 2589 28. Jun 2016 red5.xml > > > -rw-r----- 1 andreas users 628 25. Feb 2014 tomcat-users.xml > > > -rw-r----- 1 andreas users 661 25. Feb 2014 truststore.jmx > > > > > > Andreas > > > > > > > > > Maxim Solodovnik <solomax...@gmail.com> schrieb am 07.04.20 um > 12:51:00 > > > Uhr: > > > > > > > You All right :)) > > > > > > > > Version 4.0.x is shipped with HTTPS turned OFF out-of-the-box > > > > Version 5.0.x has HTTPS turned ON by default > > > > > > > > Main site contains instructions for 5.0.x > > > > > > > > There is no server.xml for version 4.0.x, it uses `embedded tomcat` > and > > > > it's own config files > > > > > > > > On Tue, 7 Apr 2020 at 03:52, Zenon Panoussis <ora...@provocation.net> > > > > wrote: > > > > > > > > > > > > > > > Ok, thank you. I read https://openmeetings.apache.org/HTTPS.html > > > > and > > > > > what I don't > > > > > > understand is that om does not listen on port 5443 after > starting. > > > > > > > > > > Out of the box, it does. If you can't access it on 5443, > > > > > check your firewall. > > > > > > > > > > > <quote> > > > > > > Self-signed certificate > > > > > > This option is available out-of-the-box, just follow the URL: > > > > > https://localhost:5443/openmeetings > > > > > > </quote> > > > > > > > > > > I'm only guessing now: is OM running on the same machine > > > > > as your browser? If not, you need to change or remove the > > > > > "address" statement in the <Connector port="5443"... stanza > > > > > in $OM_HOME/conf/server.xml. Something like changing > > > > > > > > > > <Connector address="localhost" port="5443" > > > > > protocol="org.apache.coyote.http11.Http11NioProtocol" > > > > > maxThreads="150" SSLEnabled="true" > > > > > keystoreFile="conf/keystore" keystorePass="openmeetings" > > > > > clientAuth="false" sslProtocol="TLS" /> > > > > > > > > > > to > > > > > > > > > > <Connector port="5443" > > > > > protocol="org.apache.coyote.http11.Http11NioProtocol" > > > > > maxThreads="150" SSLEnabled="true" > > > > > keystoreFile="conf/keystore" keystorePass="openmeetings" > > > > > clientAuth="false" sslProtocol="TLS" /> > > > > > > > > > > That will allow OM to also bind on the machine's external > > > > > IP-address, so that it can be reached from other machines. > > > > > See https://tomcat.apache.org/tomcat-8.5-doc/config/http.html > > > > > for more detail. > > > > > > > > > -- Best regards, Maxim
