Rocketchat direct call

[StefanU]

Please insert the screenshots in their original size. You can’t see anything like that.
Then you can click on it and the screenshot will be displayed large.

Stefan

[ATSrl]

Hi Stefan and Ralf,
I apologise for the quality of the images. I send them again and summarise the problem.

1. We have applied the suggested settings as shown in the image below
   
   
   .
   (If I failed to upload the correct resolution, I will show a zoom)
   
   
   
   In this case, EGW starts in https but does not work.
   
   
   
   (zoom again)
   
   
   
   actually EGW continues to utilise http
   
   
   
   Am I doing something wrong?
   Gabriele

[RalfBecker]

Sorry, I don’t to understand what you’re trying to archive

My understanding was an installation running secure with a valid certificate, but maybe I’m wrong.
(You will never get a (valid) certificate for https://10.0.0.45/!)

Ralf

[ATSrl]

Hi Ralf
thanks for your help. If I understand correctly, in order to have a valid certificate, the website https://sitename must be exposed in internet. However, for reasons related to our clients we cannot have internal information accessible via internet. For this reason EGW, Jitsi, RochetChat are hosted on our servers and are not exposed to the outside world.
Do you think it is possible to set EGW to work with a .local? domain ?
Thanks
Gabriele

[RalfBecker]

Do you think it is possible to set EGW to work with a .local? domain ?

EGroupware works with everything, thought you want a valid certificate for the used domain in order that current browsers are willing to frame your Jitsi Server, which uses https.

Multiple solutions are possible:

• cheapest and quickest by a commercial certificate and install it
• use a DNS challenge with Let’s Encrypt
• only temporary open http for Let’s Encrypt
• use the same method you already used for your Jitsi server to get certificate

Ralf

[ATSrl]

Ciao Ralf … no joy

trying to make EGW work in https I created a third level domain on our provider and a rule on the internal firewall and exposed the https services by doing a nat on 443. I have modified the configuration of egw by inserting the usrl https://egroupware.atsrl.net.
Despite everything, the portal continues to respond in http and on port 80, as if it ignored the settings provided.

Is there a way to specify paths to specify where ssl certificates are located?
To test the system we installed another test portal using the same nat which responds correctly in https
so …
are there any other settings I need to check/change?

Thanks again