Hmhhh – i cannot find the typo. Of Course
ADD THIS LINE --> Is just the intro to what has to be added in this line. I cannot say if this is the best way to describe it, but it might be understandable? Best wishes POW Gesendet von Mail<https://go.microsoft.com/fwlink/?LinkId=550986> für Windows 10 Von: K. Kamhamea<mailto:[email protected]> Gesendet: Dienstag, 5. Mai 2020 19:43 An: [email protected]<mailto:[email protected]> Betreff: Re: OpenMeetings - switch to port 443 Very nice, but please edit this line it contains probably a typo ADD THIS LINE --> AmbientCapabilities=CAP_NET_BIND_SERVICE Am Di., 5. Mai 2020 um 19:32 Uhr schrieb Peter-Otto Weber <[email protected]<mailto:[email protected]>>: 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
