Hello Andreas, you can use Apache config from here https://stackoverflow.com/questions/51721771/apache-openmeetings-4-0-4-csrf-attack-when-using-apache2-as-proxypass to get https for free :))
According to ports: 9999 - JMX port - should be blocked 1935 - used to send Audio/Video, even ALLOW it, OR REJECT, in latter case Apache will tunnel multimedia traffic via port 443 On Mon, 6 Apr 2020 at 02:15, ratatouille <[email protected]> wrote: > Hello! > > I startet openmeetings-4.0.10 with ./red5.sh, installed it and can > connect. > > Now I want to use https within the browser to connect to openmeetings > but netstat does not show it is listening on port 5443. > > tcp 0 0 :::5080 :::* > LISTEN 30382/java > tcp 0 0 :::5701 :::* > LISTEN 30382/java > tcp 0 0 :::9999 :::* > LISTEN 30382/java > tcp 0 0 :::1935 :::* > LISTEN 30382/java > > I am not shure at the moment what ports 5701, 9999 and 1935 are used for. > > What is the right way to use https? Usually all requests to our apache > server > are redirected to https and I had to create an exeptionrule for > openmeetings. > > Thank you for any help! > > Regards > > Andreas > -- Best regards, Maxim
