Hi, Yes I am sure. Actually, I could not have a certificate for www.domain.eu<http://www.domain.eu> but just for domain.eu (the website is not reachable at www.domain.eu<http://www.domain.eu>)
The certificate was delivered by SSL Labs after I installed CertBot on an Apache Server... I should say "on the LAMP server where I installed OpenMeetings". I followed those instructions: https://certbot.eff.org/lets-encrypt/ubuntubionic-apache ... and I configured so that the whole "domain.eu" should use https instead of http. BUT : 1/ When I connect to https://domain.eu, the certificate is verified by "Let's Encrypt". 2/ When I connect to https://domain.eu:5443/openmeetings, the certificate correspond to a self-signed one. I assume that it is due to the port, which does not correspond to HTTP/HTTPS protocols ? Sincerely, Xavier ________________________________ De : Stefan Kühl <ste...@quatrekuehl.eu> Envoyé : jeudi 4 juillet 2019 15:16 À : user@openmeetings.apache.org Cc : Xavier M Objet : Re: Log-in and security Hi, are you sure that you request your certificate also for domain.eu or only for www.domain.eu<http://www.domain.eu>. You should check this. Sometimes webhoster only use the www adresses for certificates. Greetz Stefan Am 04.07.2019 14:18, schrieb Xavier M: Hi everybody, I'm quite sure that the answer is already somewhere, but I couldn't find it... After having installed OM on a web-server, the "written" way to access to the log-in is following, according to Alvaro's tuto: https://localhost:5443/openmeetings If OM is installed on a web server, let's say "domain.eu", it works correctly with: https://domain.eu:5443/openmeetings But the user will get a warning for security reason, even if domain.eu works with https, since the common certificates will not work with this port. I stated that following URL worked for the "demo version": https://om.alteametasoft.com/openmeetings Does anyone know how this was done? I would like to avoid the use of the port 5443 with the warning. Have a good day! Xavier
