Hello, I have built LibreOffice Online 5.3.3 on Debian 8.8. It seems to run fine but when I try to edit a document, I get popup saying "Can't connect to document" and I see this in loolwsd.log: wsd-16132-16137 0:00:10.477131 [ client_ws_0001 ] ERR Error in client request handler: SSL Exception| wsd/LOOLWSD.cpp:993 loolwsd uses a valid Let's Encrypt certificate and I don't get any SSL error elsewhere. It seems to happen after this WS payload has been received: statusindicator: ready The browser then receives a strange payload containing only "é" and then the connection is closed with a 1001 code. I don't get any error in the browser console (except for a missing branding.css).
Could you check if the bug occurs with 5.4beta1 or with build of master branch of LibreOffice Online?
I tried building/running LibreOffice Online 5.4.0 with LibreOffice 5.4.0.0.beta1 but I get other, maybe unrelated, errors: loolforkit version details: 5.4.0 - 3cb12a2 office version details: { "ProductName": "LibreOfficeDev", "ProductVersion": "5.4", "ProductExtension": ".0.0.beta1", "BuildId": "8672113ead4e403c55e31b1d9a3d1e0f3b299577" } ...]: File not found| wsd/LOOLWSD.cpp:1685oll ] ERR #25 Exception while processing incoming request: [GET /hosting/discovery HTTP/1.1 So I can't tell if the SSL error is still there.
Those logs aren't very informative, however when I tried to reproduce, it was missing the cache directory: /usr/local/var/cache/libreoffice-online . Please create it manually, set the access rights correctly, and try again.
Thanks but the cache directory does exist and is writeable but I still get the same error.
In that case could you share more of the error? In comment 2 it's missing which file wasn't found.
Unfortunately what I posted is the full error I get when I start loolwsd then starting then try to connect to open a document in Owncloud. The logs don't tell me anything about the file it's trying to find. I tried loading /hosting/discovery manually with curl and it just loads forever without returning anything (and I get the same error in the logs).
Did you try simply a make run in LO Online first, and then accessing the link to the test document?
I just noticed there is a "trace" verbosity level which helps a lot in debugging these issues. Turns out the 5.3 SSL issue was due to my Apache configuration. And 5.4 was not finding discovery.xml for some reason. I now have other unrelated issues but I will close this bug. Thanks for your help and sorry for not figuring that earlier.