I to had the same issue, 5443 was not working out of the box. I resolved by following this guide.
https://om.alteametasoft.com/openmeetings/docs/RTMPSAndHTTPS.html#SSL_for_the_web_interface -----Original Message----- From: ratatouille [mailto:[email protected]] Sent: Monday, April 6, 2020 2:40 PM To: [email protected] Subject: Re: A Question about Tomcat Hello! Zenon Panoussis <[email protected]> schrieb am 06.04.20 um 20:38:12 Uhr: > > When I start openmeetings with red5.sh an instance of tomcat is startet, > > right? > > And when I connect to port 5080 I connect to tomcat, right? > > > Is the apache webserver involved in all this that is running on the same > > machine? > > No. tomcat *is* the webserver. If you're not using apache for > something else, you can switch it off. 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. <quote> Self-signed certificate This option is available out-of-the-box, just follow the URL: https://localhost:5443/openmeetings </quote> Andreas
