This probably doesn't work with M4. I did all the installations as describe for M4 - Installation OpenMeetings 5.0.0-M4 on Ubuntu 18.04 LTS.pdf - Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4.pdf and edited openmeetings.service accordingly, but as soon as I change port 5443 -> 443 in server.xml system crashes
When I browse https://mydomain:443 [image: grafik.png] Just changing back server.xml 443 -> 5443 solves the problem, so https://mydomain:5443 can be accessed. Am Di., 5. Mai 2020 um 19:32 Uhr schrieb Peter-Otto Weber < cyber...@hotmail.de>: > 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 >
