@icewind I am having the same problem that the application opens as described by archit3cct but then get the unexpected connection error.
The debug log shows:
It did create the (empty) file:
The discovery shows the XML output as described by lukas.
The only difference is that I made is with the docker command to start it, to point to a different IP and port number:
docker run -t -d -p 192.168.0.245:8082:9980 -e "domain=cloud\.nextcloud\.com" --cap-add MKNOD collabora/code
I would not expect that would be a real issue.
Below is a little diagram how I have set it up currently:
Traffic comes in from internet to the apache (proxy) server which translates several subdomains to the relevant VM’s. Both Nextcloud and Collabora are installed on the same VM but Collabora has the server IP address instead of localhost. This since Apache2 is running on a different VM.
When running the docker without -d I can see the following lines:
wsd-00020-03 00:00:59.652406 [ client_req_hdl ] Request from 192.168.0.241:34244: GET /lool/ws/https://cloud.mydomain.com/apps/richdocuments/wopi/files/539952?access_token=MmDqKhmaclv3bc6t3G
kcIix6JBuXVEpG HTTP/1.1 / Host: office.mydomain.com / Pragma: no-cache / Cache-Control: no-cache / Origin: https://office.mydomain.com / Sec-WebSocket-Version: 13 / DNT: 1 / User-Agent: Mozi
lla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 / Accept-Encoding: gzip, deflate, sdch, br / Accept-Language: en-GB,en-US;q=0.8,en;q=0.6,
nl;q=0.4 / Sec-WebSocket-Key: Px+cnXf6eTLKB1uatw7XYA== / Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits / X-Forwarded-For: 192.168.0.1 / X-Forwarded-Host: office.mydomain.com / X-Forwarded-Server: office.mydomain.com / Upgrade: WebSocket / Connection: Upgrade
then few lines lower:
kit-00101-00 00:01:10.851174 [ loolkit ] link("/opt/collaboraoffice5.1/CREDITS.fodt","/opt/lool/child-roots/101/lo/CREDITS.fodt") failed. Exiting. (errno: Operation not permitted)
frk-00029-00 00:01:11.471271 [ loolforkit ] Child 101 has exited, removing its jail '/opt/lool/child-roots/101'
wsd-00020-03 00:01:15.757649 [ client_ws_0001 ] getNewChild: No live child, forking more.
wsd-00020-03 00:01:15.757795 [ client_ws_0001 ] getNewChild: Timed out while waiting for new child.
wsd-00020-03 00:01:15.757865 [ client_ws_0001 ] Failed to get new child. Service Unavailable.
wsd-00020-03 00:01:15.758209 [ client_ws_0001 ] ClientRequestHandler::handleRequest: WebSocketErrorMessageException: Service is unavailable. Please try again later and report to your adminis
trator if the issue persists.
I am bit unclear now how to tackle this issue.