Hi Maxim,

thanks for your quick response.

Yes, I tried those.
Didn’t work.
So before I tell you everything I tried so far: can I use a config-file instead 
of the keystore?
Just like in OM5, where I can alter the server.xml and edit the path to the 
certificates?



Best wishes,
Alex

Von: Maxim Solodovnik <[email protected]>
Gesendet: Freitag, 12. Juni 2020 10:41
An: Openmeetings user-list <[email protected]>
Betreff: Re: HTTPS with OpenMeetings 4 (4.0.10)

The instructions are shipped with every OM release
And can be found for ex. here 
https://om.alteametasoft.com/openmeetings/docs/RTMPSAndHTTPS.html

On Fri, 12 Jun 2020 at 15:31, Ninnig, Alexander 
<[email protected]<mailto:[email protected]>>
 wrote:
Hello,

I’m really sorry to bother, but I can’t get HTTPS working with OpenMeetings 4. 
The site (https/5443) cannot be displayed.

I had the same problem with OpenMeetings 5, until someone told me not to use 
the keystore, but to alter the server.xml instead and change the lines into 
something like that:
    <Connector port="5443"
    SSLEnabled="true">
        <SSLHostConfig>
            <Certificate certificateFile="/etc/mycertfolder/server.pem"
                         certificateKeyFile="/etc/mycertfolder/key.pem"
                         certificateChainFile="/etc/mycertfolder/chain.pem"
                            sslProtocol="TLS"/>
        </SSLHostConfig>
    </Connector>
As I said, that worked with OpenMeetings 5.
Unfortunately, OM5 is not production-ready yet, but I need a solution now.
And unfortunately, there is no server.xml in OM4.
I also searched the whole filesystem for strings like „Connector“, but I got no 
match.

Before I tell you everything I tried in ordner to make the keystore work:
Can you tell me, If there is a similar solution as the one, mentioned above, in 
OpenMeetings 4?
Meaning: can I simply edit a config-file and provide this config with the paths 
to my certificates?
Or do I have to use the keystore?

If I have to use the keystore, I will describe to you what I tried so far.

Best wishes,
Alex





--
Best regards,
Maxim

Reply via email to