Description: First posting here. Unsure if right place but my usual OwnCloud (https://central.owncloud.org/t/) forum has nothing relevant NextCloud is reporting similar error (https://help.nextcloud.com/t/why-might-collabora-code-docker-image-not-be-responding-to-http-s/52818) is unresolved but it doesn't seem to be concerning OC/NC rather a collabora/CODE docker setup error. Initially I setup collabora server as app on Ubuntu 18.04 using this guide https://www.collaboraoffice.com/code/#getting_set_up, but couldn't get it to accept https (owncloud server) to http (collabora). So I setup collabora using docker instead as per above collabora instructions, but kept getting "cURL error 7: Failed to connect to 192.168.1.106 port 9980: Connection refused" from owncloud. SETUP (two servers machines on LAN) A. Owncloud https server 10.0.3 on Raspbian 4.1471-v7 with Apache/2.4.25 with 10.1.37-MariaDB-0+deb9u1 - Raspbian 9.0 B. Ubuntu 18.04.2 LibreOffice server with Docker Collabora/code:latest and tried 4.0.1.1 OUTPUT on collabora docker server ab@acer:~$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 26e783f9cc14 collabora/code:4.0.1.1 "/bin/sh -c 'bash st…" About an hour ago Up 12 seconds 127.0.0.1:9980->9980/tcp collabora ab@acer:~$ curl -vk https://127.0.0.1:9980 * Rebuilt URL to: https://127.0.0.1:9980/ * Trying 127.0.0.1... * TCP_NODELAY set * Connected to 127.0.0.1 (127.0.0.1) port 9980 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * (304) (OUT), TLS handshake, Client hello (1): * OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 127.0.0.1:9980 * Closing connection 0 curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 127.0.0.1:9980 ab@acer:~$ docker logs collabora | grep SSL wsd-00029-00029 2019-06-26 09:48:22.063852 [ loolwsd ] INF SSL support: SSL is enabled.| wsd/LOOLWSD.cpp:987 wsd-00029-00029 2019-06-26 09:48:23.812395 [ loolwsd ] INF SSL Cert file: /etc/loolwsd/cert.pem| wsd/LOOLWSD.cpp:1169 wsd-00029-00029 2019-06-26 09:48:23.812626 [ loolwsd ] INF SSL Key file: /etc/loolwsd/key.pem| wsd/LOOLWSD.cpp:1172 wsd-00029-00029 2019-06-26 09:48:23.812888 [ loolwsd ] INF SSL CA file: /etc/loolwsd/ca-chain.cert.pem| wsd/LOOLWSD.cpp:1175 wsd-00029-00029 2019-06-26 09:48:23.813115 [ loolwsd ] INF SSL Cipher list: | wsd/LOOLWSD.cpp:1178 wsd-00029-00029 2019-06-26 09:52:45.055432 [ loolwsd ] INF SSL support: SSL is enabled.| wsd/LOOLWSD.cpp:987 wsd-00029-00029 2019-06-26 09:52:46.807582 [ loolwsd ] INF SSL Cert file: /etc/loolwsd/cert.pem| wsd/LOOLWSD.cpp:1169 wsd-00029-00029 2019-06-26 09:52:46.807827 [ loolwsd ] INF SSL Key file: /etc/loolwsd/key.pem| wsd/LOOLWSD.cpp:1172 wsd-00029-00029 2019-06-26 09:52:46.808063 [ loolwsd ] INF SSL CA file: /etc/loolwsd/ca-chain.cert.pem| wsd/LOOLWSD.cpp:1175 wsd-00029-00029 2019-06-26 09:52:46.808278 [ loolwsd ] INF SSL Cipher list: | wsd/LOOLWSD.cpp:1178 wsd-00029-00029 2019-06-26 10:51:24.188710 [ loolwsd ] INF SSL support: SSL is enabled.| wsd/LOOLWSD.cpp:987 wsd-00029-00029 2019-06-26 10:51:25.999395 [ loolwsd ] INF SSL Cert file: /etc/loolwsd/cert.pem| wsd/LOOLWSD.cpp:1169 wsd-00029-00029 2019-06-26 10:51:25.999631 [ loolwsd ] INF SSL Key file: /etc/loolwsd/key.pem| wsd/LOOLWSD.cpp:1172 wsd-00029-00029 2019-06-26 10:51:25.999847 [ loolwsd ] INF SSL CA file: /etc/loolwsd/ca-chain.cert.pem| wsd/LOOLWSD.cpp:1175 wsd-00029-00029 2019-06-26 10:51:26.000038 [ loolwsd ] INF SSL Cipher list: | wsd/LOOLWSD.cpp:1178 I've tried editing the Apache reverse proxy with several variants as proposed by collabora, adding IPs to /etc/hosts, disabling UFW, allowing docker0 onto UFW and editing the loolwsd.xml inside the container with variants proposed in collabora setup. I guess I'm missing something simple but could anyone confirm if there is a bug? Andrew Steps to Reproduce: 1. launch collabora docker ab@acer:~$ docker run -t -d -p 127.0.0.1:9980:9980 -e "domain=awsbarker.ddns.net" --name collabora --cap-add MKNOD --restart always collabora/code 2. Click 'office' in owncloud Collabora Online: Cannot connect to the host "https://192.168.1.106:9980". Please ask your administrator to check the Collabora Online server setting. The exact error message was: cURL error 7: Failed to connect to 192.168.1.106 port 9980: Connection refused 3. check collabora status ab@acer:~$ curl -k https://127.0.0.1:9980 curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 127.0.0.1:9980 Actual Results: owncloud fails to connect to collabora server Expected Results: owncloud connect to collabora server Reproducible: Always User Profile Reset: No Additional Info: ii libreoffice-common 1:6.0.7-0ubuntu0.18. all office productivity suite -- arch-independent files ii libreoffice-core 1:6.0.7-0ubuntu0.18. amd64 office productivity suite -- arch-dependent file
Please give a try to recent LO version (6.1.4). You can find it at LO ppa (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa) Indeed, 6.0 is EOL.
Thanks Julien for quick reply. I'll try that I didn't realise that LO version would impact the collabora/code docker.
Andrew: Rereading all this, it seems very specific to Collobora part. Michael: since it concerns Collabora version, thought you might be interested in this one.
I tried the LO update: ab@acer:~$ dpkg -l libreoffice-core ============================================================== ii libreoffice-core 1:6.2.4-0ubuntu0.18. amd64 office productivity suite -- arch-dependent files But still get SSL error. ab@acer:~$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ed46e0d035a0 collabora/code:4.1-snapshot "/bin/sh -c 'bash /r…" 17 hours ago Up 4 minutes 127.0.0.1:9980->9980/tcp priceless_visvesvaraya ab@acer:~$ curl -k https://127.0.0.1:9980 curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 127.0.0.1:9980 I updated/edited version in bug report. Let me know what other logs you might need. Andrew
[Automated Action] NeedInfo-To-Unconfirmed
Does the same error happen with the docker image provided by TDF? https://hub.docker.com/r/libreoffice/online/
Dear Andrew, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Andrew, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp