https-certificate - Lets encrypt

2019-05-14 Thread René Scholz
Hello, I try to import an lets encrypt-certificate into OM 5-M2. With a few commands I have 4 certificates (wildcard-certificate): cert.pem chain.pem fullchain.pem privkey.pem I try to edit the server.xml, remark the original lines for "connector port 5443" and replace it with:

Re: https-certificate - Lets encrypt

2019-05-14 Thread Maxim Solodovnik
Maybe "certificateChainFile="conf/chain.pem"" should be fullchain.pem? Additionally you can turn ON SSL debug logging to get more details On Tue, 14 May 2019 at 20:33, René Scholz wrote: > > Hello, > > I try to import an lets encrypt-certificate into OM 5-M2. > > With a few commands I have 4 cer

Re: https-certificate - Lets encrypt

2019-05-14 Thread R. Scholz
Hello and good morning, yesterday in the evening I had successfully installed the lets encrypt-certificate. Great. If anybody wants a "step-by-step-receipt" to implement a lets-encrypt certificate in a computer behind a firewall (no access over port 80): Send me a hint. I have some notes (i

OM-access with 2 subdomains

2019-05-14 Thread R. Scholz
Hello, I want to access my OM-instance over 2 Subdomains. One subdomain use port 5443 (with the correct certificate) the other over port 5444. When I send an invitation the link-generator use the setting in the OM-configuration. Thats clear. My Idea: Is it possible to implement "a wildcard"