Closed whlsxl closed 3 years ago
tiredofit
commented
5 years ago Can you check to see if it does indeed exist in /etc/loolwsd What we might need here is to get you to set DEBUG_MODE=TRUE and then post the entire container startup output.
whlsxl
commented
5 years ago There are loolkitconfig.xcu and loolwsd.xml in /etc/loolwsd.
I found, I already set - "extra_params=--o:ssl.enable=false" in docker-compose.yml environment, but in /etc/loolwsd/loolwsd.xml , ssl is enable
<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">true</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> </hpkp> </ssl>
whlsxl
commented
5 years ago After I set ssl enable false manually, collabora boot successful, but... new error...
whlsxl
commented
5 years ago The extra_params not come into effect still a problem.
whlsxl
commented
5 years ago Hey @tiredofit ,
I find the way to user extra_params, The official Dockerfile start loolwsd use extra_params as params https://github.com/CollaboraOnline/Docker-CODE/blob/master/scripts/start-libreoffice.sh#L42
tiredofit
commented
5 years ago Right on! I'll update this on Monday and start the build. It takes about 12 hours from my start of build to complete, will advise when a new version is posted. In the meantime if you wanted to see if it worked:
Enter in the container:
s6-svc -d /var/run/s6/services/10-loolwsd
nano /etc/s6/services/10-loolwsd/runAdd the extra_params part as per the official Dockerfile
Then restart the service s6-svc -u /var/run/s6/services/10-loolwsd - That should get you going for the time being!
whlsxl
commented
5 years ago Now, the collabora is worked, but the access through traefik is not work.
when curl https://collabora_url in nextcloud bash, got No route to host.
Someone said this is firewall problem, still no solution.
tiredofit
commented
5 years ago I've got it working. I'm just building a new version of the image to set SSL parameters and will post here when ready with details and configuration.
tiredofit
commented
5 years ago OK. I've pushed a new version to Docker hub tiredofit/libreoffice-online:1.5 or latest that will get you going on Traefik, also added a tonne more configuration options for you for the configuration file to avoid having to use the EXTRA PARAMETERS option.
Heres how to get it going via ENV Vars:
ENABLE_TLS=FALSE
ENABLE_TLS_REVERSE_PROXY=TRUEIn your docker-compose.yml:
labels:
- traefik.enable=true
- traefik.frontend.rule=Host:libreoffice.example.com
- traefik.port=9980
- traefik.protocol=http
- traefik.docker.network=proxy
- traefik.backend=libreoffice-online-appLet me know how you make out.
After set - "DONT_GEN_SSL_CERT=true" & - "extra_params=--o:ssl.enable=false" still got this error