Hab endlich Collabora zum laufen bekommen mit meinem Ubuntu 16.04 Server. Aber auch nur nachdem ich den Kernel einem Update unterzogen habe.
Zumindest läuft es fast, nur Collabora kann nicht auf die Dokumente zugreifen und bearbeiten.
Unfortunately I can confirm this problem.
This is my Docker log:
Generating RSA private key, 2048 bit long modulus
…+++
…+++
e is 65537 (0x10001)
Generating RSA private key, 2048 bit long modulus
…+++
…+++
e is 65537 (0x10001)
Signature ok
subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost
Getting CA Private Key
loolwsd version details: 1.9.6 - 1.9.6
loolforkit version details: 1.9.6 - 1.9.6
wsd-00025-0026 0:00:02.048854 [ client_ws_0001 ] ERR ClientRequestHandler::handleClientRequest: BadRequestException: Invalid or unknown request.
office version details: { “ProductName”: “Collabora Office”, “ProductVersion”: “5.1”, “ProductExtension”: “.10.11”, “BuildId”: “7512f1e1867672c06d987a94edb07f0a7ea0fc1e” }
wsd-00025-0029 0:00:45.726502 [ client_ws_0003 ] ERR ClientRequestHandler::handleClientRequest: BadRequestException: Invalid or unknown request.
wsd-00025-0028 0:00:45.955727 [ client_req_hdl ] ERR FileServerRequestHandler: File not found: /usr/share/loolwsd//loleaflet/dist/node_modules/jquery-ui/themes/ui-lightness/images/ui-bg_highlight-soft_100_eeeeee_1x100.png
wsd-00025-0028 0:01:26.196959 [ client_ws_0004 ] ERR ClientRequestHandler::handleClientRequest: BadRequestException: Invalid or unknown request.
wsd-00025-0028 0:03:26.918873 [ client_ws_0005 ] ERR ClientRequestHandler::handleClientRequest: BadRequestException: Invalid or unknown request.
wsd-00025-0026 0:07:33.566498 [ client_ws_0006 ] ERR ClientRequestHandler::handleClientRequest: BadRequestException: Invalid or unknown request.
wsd-00025-0028 0:07:33.775501 [ client_req_hdl ] ERR FileServerRequestHandler: File not found: /usr/share/loolwsd//loleaflet/dist/node_modules/jquery-ui/themes/ui-lightness/images/ui-bg_highlight-soft_100_eeeeee_1x100.png
wsd-00025-0028 0:08:51.552925 [ client_ws_0007 ] ERR ClientRequestHandler::handleClientRequest: BadRequestException: Invalid or unknown request.
This is the nextcloud log:
Error PHP chmod(): Operation not permitted at /var/www/nextcloud/lib/private/Log/Owncloud.php#117 2016-11-03T09:17:58+00:00
Error PHP Undefined index: dir at /var/www/nextcloud/apps/richdocuments/controller/documentcontroller.php#364 2016-11-03T09:17:58+00:00
Error PHP Undefined index: filename at /var/www/nextcloud/apps/richdocuments/controller/documentcontroller.php#363 2016-11-03T09:17:58+00:00
Error PHP chmod(): Operation not permitted at /var/www/nextcloud/lib/private/Log/Owncloud.php#117 2016-11-03T08:49:29+00:00 marcel
Error PHP Undefined index: dir at /var/www/nextcloud/apps/richdocuments/controller/documentcontroller.php#364 2016-11-03T08:49:29+00:00
Error PHP Undefined index: filename at /var/www/nextcloud/apps/richdocuments/controller/documentcontroller.php#363 2016-11-03T08:49:29+00:00
Error PHP BadMethodCallException: No settings enabled at /var/www/nextcloud/apps/activity/lib/Data.php#204
File permissions are checked and owned by www-data.
I tried to investigate with chrome’s integrated functions and get this:
WebSocket connection to ‘wss://office.xxx.xx/lool/https%253A%252F%252Fcloud.xxx…7%3Faccess_token%3DNGvj5FQ71oagSiu0Y9IXVC7HyvoCLRaw%26permission%3Dedit/ws’ failed: Error during WebSocket handshake: Unexpected response code: 400
Issuing token for lars file 30719, version 0 owned by lars, path /Privater PC Reperaturservice.odt: 2QgG4mvoohnFkwyuAwLiRqooHRJqpbwQ 2016-11-03T14:07:57+00:00 lars
Debug richdocuments File with 30719 has updatable set to true 2016-11-03T14:07:57+00:00 lars
Debug richdocuments Generating WOPI Token for file 30719, version 0. 2016-11-03T14:07:57+00:00 lars
Info admin_audit File accessed: "/Privater PC Reperaturservice.odt" 2016-11-03T14:07:57+00:00 lars
Debug richdocuments Testgroups are []
AH01144: No protocol handler was valid for the URL /lool/https%3A%2F%2Fcloud.land-laeufer.de%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F31089?access_token=57Kx9X05w5KP5EZYtFt1aDUvImEi9p3F&permission=edit/ws. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.w @ bundle.js:57
https://cloud.land-laeufer.de/loleaflet/1.9.8/node_modules/jquery-ui/themes/ui-lightness/images/ui-bg_highlight-soft_100_eeeeee_1x100.png Failed to load resource: the server responded with a status of 404 ()
VM2438:35 WebSocket connection to 'wss://cloud.land-laeufer.de/lool/https%253A%252F%252Fcloud.land-laeufer.de%…8%3Faccess_token%3DoOHzWCxv6Zl0MsDtJq4EvhaPl11g8eA6%26permission%3Dedit/ws' failed: Error during WebSocket handshake: Unexpected response code: 500WrappedWebSocket @ VM2438:35
Es wäre mir auch sehr lieb, das Geheimnis dahinter zu erfahren, damit es läuft. Habe einen Nutzer eingerichtet, wie gefordert. Nur selbst mit dem ist es nicht getan… Läuft auf Nginx. Also wie bei dir Lars. Jedenfalls weiß ich nicht weiter.
Musste, damit das Zertifikat richtig erkannt wird mein Letsencrypt Zertifikat in das ca-bundle.crt von Nextcloud migrieren. cat crt1.crt >> nextcloud/resources/ca-bundle.crt
Der docker Container läuft unter einem Systemuser von Ubuntu.