Unable to start Collabora-key container

RalfBecker 2020-04-27 07:03:59 UTC #21

Collabora has an option in loolwsd.xml telling it to be behind a proxy and it’s ok to receive the incomming trafic http:

github.com

EGroupware/build.opensuse.org/blob/master/server:eGroupWare/egroupware-collabora-key/egroupware-collabora-key/loolwsd.xml#L88


    <host desc="Ditto, but as IPv4-mapped IPv6 addresses">::ffff:192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
    <host desc="The IPv4 loopback (localhost) address.">127\.0\.0\.1</host>
    <host desc="Ditto, but as IPv4-mapped IPv6 address">::ffff:127\.0\.0\.1</host>
    <host desc="The IPv6 loopback (localhost) address.">::1</host>
  </post_allow>
  <frame_ancestors desc="Specify who is allowed to embed the LO Online iframe (loolwsd and WOPI host are always allowed). Separate multiple hosts by space."></frame_ancestors>
</net>


<ssl desc="SSL settings">
    <enable type="bool" desc="Controls whether SSL encryption is enable (do not disable for production deployment). If default is false, must first be compiled with SSL support to enable." default="true">false</enable>
    <termination desc="Connection via proxy where loolwsd acts as working via https, but actually uses http." type="bool" default="true">false</termination>
    <cert_file_path desc="Path to the cert file" relative="false">/etc/loolwsd/cert.pem</cert_file_path>
    <key_file_path desc="Path to the key file" relative="false">/etc/loolwsd/key.pem</key_file_path>
    <ca_file_path desc="Path to the ca file" relative="false">/etc/loolwsd/ca-chain.cert.pem</ca_file_path>
    <cipher_list desc="List of OpenSSL ciphers to accept" default="ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH"></cipher_list>
    <hpkp desc="Enable HTTP Public key pinning" enable="false" report_only="false">
        <max_age desc="HPKP's max-age directive - time in seconds browser should remember the pins" enable="true">1000</max_age>
        <report_uri desc="HPKP's report-uri directive - pin validation failure are reported at this URL" enable="false"></report_uri>
        <pins desc="Base64 encoded SPKI fingerprints of keys to be pinned">
        <pin></pin>
        </pins>

Collabora need to be told with these configuration, if you use SSL and/or proxy. The above link is from our packages, which assumes https used by browser, but terminated before it reaches Collabora by a proxy.

These are all solvable problems, but - sorry to say - I don’t the time to solve them with mile long threads here in the forum.

Ralf

J_Roeleveld 2020-05-12 07:00:06 UTC #22

Ralf,

With those settings, I did not get it working.
I did manage to resolve the issue by applying the settings in the “nginx.conf” file directly on the primary webserver and exposing all the docker-ports to the network.
Only had to keep the “egroupware-nginx” container running to proxy the static files to.

Many thanks for all the help and patience you provided.

–
Joost