With this config import is redundant you can use your keys as-is :) On Sun, 13 Oct 2019 at 21:11, Yah's Global Kingdom <[email protected]> wrote:
> Thanks for the information, if I might ask which of these keys did you > import into your keystore for openmeetings? > > On Sat, Oct 12, 2019 at 1:36 PM R. Scholz < > [email protected]> wrote: > >> Hello, >> >> this is the part in my server.xml in the conf-dir of my openmeeting I use >> without problems: >> >> <Connector port="5443" >> SSLEnabled="true"> >> <SSLHostConfig> >> <Certificate certificateFile="/etc/letsencrypt/live/ >> subdomain.domain.de/cert.pem" >> certificateKeyFile="/etc/letsencrypt/live/ >> subdomain.domain.de/privkey.pem" >> certificateChainFile="/etc/letsencrypt/live/ >> subdomain.domain.de/fullchain.pem" /> >> </SSLHostConfig> >> </Connector> >> >> With best regards, >> >> René >> >> >> >> Am 12.10.2019 um 17:35 schrieb Yah's Global Kingdom: >> >> Ok understood for the VOIP implementation. Hopefully, there will be time >> for in the near future as it was feature that was really appreciated and >> used. >> On a different note. I am using LetsEncrypt for ssl certificates. The >> wiki at https://openmeetings.apache.org/HTTPS.html does not seem to >> apply as you can not submit a .csr file to lets encrypt and it only works >> on port 443. I have changed /conf/server.conf to 443 but the server still >> refuses to connect. Are there any instructions for how to make OM 5.0.0.M2 >> OR M3 work with LetEncrypt and Certbot? Thanks for all your help Maxim. >> >> On Thu, Oct 10, 2019 at 12:45 PM Maxim Solodovnik <[email protected]> >> wrote: >> >>> Yes, sure >>> unfortunately my time is very limited >>> not sure i can provide any estimates >>> >>> On Thu, 10 Oct 2019 at 09:16, Yah's Global Kingdom <[email protected]> >>> wrote: >>> >>>> Is there a plan to implement VOIP for this version of Openmeetings? >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >> -- WBR Maxim aka solomax
