Peter,

thanks for the conclusion, with the fixes from Juan I was also able to get it 
working on 443.

As in your later posts commented a problem are company firewalls.
They are much more restrictive. And in many companies the firewalls are 
maintained by externals or
Corporate IT. So it’s nearly impossible to get some ports opened in a short 
time.
The second possibility is using hosted services, but LDAP and AD can’t really 
be used then.

In home offices the home routers are not a problem in most cases.
This is our experience. As we are a smaller company firewall is under our 
control,
and we have also a test internet link to play with..

To use just port 443 is probably technical difficult, because it needs probably 
a total redesign of OM and the components in use.



Gerald






Von: Peter-Otto Weber [mailto:cyber...@hotmail.de]
Gesendet: Dienstag, 5. Mai 2020 19:33
An: user@openmeetings.apache.org
Betreff: OpenMeetings - switch to port 443

Together with Maxim and Juan (they had the brain and i had the fingers) i was 
able to configure my OpenMeetings m3 to work on Port 443.

The base system follows the guides

·         Installation OpenMeetings 5.0.0-M3 on Ubuntu 18.04 LTS.pdf
·         Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3.pdf

The main problems were with firewall and Coturn using „kurento“ as user and not 
„nobody“.

After all it was not so many things to do:

Backup /opt(open503/openmeetings.service
Backup /opt/open503/config/server.xml

Change openmeetings.service

[Service]
Type=forking
ADD THIS LINE --> AmbientCapabilities=CAP_NET_BIND_SERVICE

Change all folders /openmeetings/ to /open503/

Change User=nobody to User = kurento

Copy this file to /etc/systemd/system/openmeetings.service

Change all port 5443 to 443 in server.xml (two places)

Check firewall and open port 443 if not open as in my case 😉  )

Reboot

sudo /etc/init.d/mysql start                                 MariaDB data server
sudo /etc/init.d/kurento-media-server start           Kurento media server
sudo systemctl start openmeetings                   openmeetings

There’s still a problem with creating pid file – i will check out later…

Best wishes

POW

Reply via email to