Update: I just saw in the /opt/om/log/openmeetings.log that OpenMeetings won't start with the https Port 443 in red5.properties, so I changed it back to 5443
-- Sandro Isoletta Abteilung 4 Zentrale Dienste und IT-Dienste Referat 4.07 Schulische IT-Dienstleistungen PÄDAGOGISCHES LANDESINSTITUT RHEINLAND-PFALZ Hofstraße 257c 56077 Koblenz 0261 9702 317 it-supp...@pl.rlp.de www.pl.rlp.de Am 30.06.2015 um 13:21 schrieb Sandro Isoletta: > I did your suggested changings. > Yes, the Server is only for OpenMeetings, so I also changed the https > port in red5.properties file to 443. > > The URL of the Server is: > > https://openmeetings.bildung-rp.de/openmeetings/ > > and now I get the following error message in /var/log/apache2/error.log: > > [Tue Jun 30 13:18:08 2015] [error] (111)Connection refused: proxy: > HTTPS: attempt to connect to 192.168.199.48:5080 > (openmeetings.bildung-rp.de) failed > [Tue Jun 30 13:18:08 2015] [error] ap_proxy_connect_backend disabling > worker for (openmeetings.bildung-rp.de) > [Tue Jun 30 13:18:33 2015] [error] proxy: HTTPS: disabled connection for > (openmeetings.bildung-rp.de) > > > (192.168.199.48 is the IP Adress of the Server) > > > Regards >
