Gentlemen, In case the Java information matters at all:
~$ java -version openjdk version "11.0.6" 2020-01-14 OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed mode) ~$ sudo java -version java version "11.0.6" 2020-01-14 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.6+8-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.6+8-LTS, mixed mode) ~$ sudo update-alternatives --config java There are 3 choices for the alternative java (providing /usr/bin/java). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode 1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode * 2 /usr/lib/jvm/java-11-oracle/bin/java 1091 manual mode 3 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode And here is how Ubuntu 18.04 packages Java 10 under the Java 11 cover: ~$ sudo apt install openjdk-11-jdk openjdk-11-jdk-headless Reading package lists... Done Building dependency tree Reading state information... Done openjdk-11-jdk is already the newest version (10.0.1+10-3ubuntu1). openjdk-11-jdk-headless is already the newest version (10.0.1+10-3ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. On Wed, Apr 8, 2020 at 3:51 AM Robert Savickas <robsavic...@gmail.com> wrote: > Rene, > > Thank you. Actually, I had this type of record, as you suggest, prior to > following Alvaro's instructions. I just used my *.pem files from a previous > certificate I had for the domain. Tomcat worked plenty fine with this set > up. > > However, meeting participants could not see each other nor hear each > other. They only could see themselves. However, they could see that the > other party is trying to say something because the green frame around the > photo would glow). I thought that they could not see or hear each other > probably because Kurento was not set up with the SSL certificate. > > So, I decided to follow Alvaro's manual to the letter. His manual suggests > that I change that record for port 5443 the way that I sent it to you... > > Robert. > > > On Wed, Apr 8, 2020 at 3:23 AM René Scholz < > rene.sch...@abakus-edv-systems.de> wrote: > >> Hm, I think you need something like that in your server.xml >> So your tomcat have no chance to answer the request. >> >> <Connector port="5443". >> SSLEnabled="true"> >> <SSLHostConfig> >> <Certificate certificateFile="/etc/letsencrypt/live/FQDN/cert.pem" >> >> certificateKeyFile="/etc/letsencrypt/live/FQDN/privkey.pem" >> >> certificateChainFile="/etc/letsencrypt/live/FQDN/fullchain.pem" /> >> </SSLHostConfig> >> </Connector> >> >> Best regards, >> >> René >> >> Am 08.04.2020 um 09:18 schrieb Robert Savickas: >> >> Dear Rene, >> >> I do appreciate your quick response. Here is the relevant portion of the >> server.xml file: >> >> <Connector port="5443" >> protocol="org.apache.coyote.http11.Http11NioProtocol" >> maxThreads="150" SSLEnabled="true" >> keystoreFile="conf/my-domain.jks" keystorePass="my-password" >> clientAuth="false" sslProtocol="TLS"/> >> >> Also, I *am* running Java 11 (I saw your earlier post about that). The >> standard Ubuntu 18.04 packages java 10 under the Java 11 cover. However, I >> installed Java 11 from linuxuprising, using the Oracle file. >> >> Robert. >> >> >> On Wed, Apr 8, 2020 at 3:08 AM René Scholz < >> rene.sch...@abakus-edv-systems.de> wrote: >> >>> Hello, >>> >>> whats your config in your server.xml for port 5443? >>> >>> Best regards, >>> >>> René >>> >>> >>> >>> Am 08.04.2020 um 08:39 schrieb Robert Savickas: >>> >>> Dear friends, >>> >>> This is a bit critical for me because I was hoping to use OpenMeetings >>> to conduct my online classes at the university (I am a professor), since we >>> are all locked up at our homes due to the virus. My class is in less than >>> two days. I had set up RocketChat with Jitsi meetings previously, but I did >>> not like them. OpenMeetings is far superior. So, I am trying to move to >>> OpenMeetings by my next class the day after tomorrow. >>> >>> I have followed *verbatim* all the instructions in the two fine >>> documents by Alvaro Bustos about installing Openmeetings 5.0.0-M3 on Ubuntu >>> 18.04 and also about installing the SSL certificated and Coturn. >>> >>> Openmeetings was working OK prior to installing SSL; I was able to go to >>> https://localhost:5443/openmeetings, login, set up, etc. (In a >>> conference room, the video and sound were not transmitting, but I reckoned >>> it was because Kurento was not set up with SSL). >>> >>> The installation of SSL went very smoothly, due to the very well written >>> white paper by Alvaro. >>> >>> However, after the SSL installation, when I go to >>> https://localhost:5443/openmeetings, I get error 404: Not found, even >>> though the directory is definitely there. I reckon that a java servlet is >>> missing or incorrect, or something similar. But I do not know how to find >>> it and how to fix it. >>> >>> Telnetting into the port 5443 does show that there is service on that >>> port. Whether I telnet to localhost at 5443 or ip-address at 5443 or >>> domain-name at 5443, all respond fine. (Same is true for ports 3478 and >>> 8888.) However, when I go to https://localhost:5443/openmeetings or >>> https://ip-address:5443/openmeetings or >>> https://domain-name:5443/openmeetings, I get the 404 error. >>> >>> I would really appreciate it if there are any hints or suggestions you >>> could offer. >>> >>> Thank you. >>> Robert. >>> >>> >>> >>
