Will be happy to know how do you compile this packages, because I’m in the same boat. Thank you!
hello @Access_Forbidden, following this tutorials:
libreoffice core: Source Code | LibreOffice - Free Office Suite - Based on OpenOffice - Compatible with Microsoft
loolwsd: https://github.com/LibreOffice/online/tree/master/loolwsd
loleaflet: online/loleaflet at master · LibreOffice/online · GitHub
hello, good for you’re compiling but I think we can do it with the docker image.
I’ll continue to search why It doesn’t work
hello @guidtz, there are some things I’m wondering about (bold printed). Here are some log details from my docker container with collabora:
[ client_ws_0008 ] WOPI::CheckFileInfo header for URI [https://xxxxxxxxxx/index.php/apps/richdocuments/wopi/files/xxxxxxxxxx?access_token=xxxxxxxxxx]:
Server: nginx / Date: Mon, 01 Aug 2016 07:55:49 GMT / Content-Type: application/json; charset=utf-8 / Content-Length: 32 / Connection: close / X-Powered-By: PHP/7.0.8 / Set-Cookie: nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict / Set-Cookie: nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax / Set-Cookie: oc_sessionPassphrase=xxxxxxxxxx; path=/; secure; HttpOnly / Set-Cookie: xxxxxxxxxx; path=/; HttpOnly / Expires: Thu, 19 Nov 1981 08:52:00 GMT / Pragma: no-cache / Cache-Control: no-cache, must-revalidate / Content-Security-Policy: default-src ‘none’;script-src ‘self’ ‘unsafe-eval’;style-src ‘self’ ‘unsafe-inline’;img-src ‘self’ data: blob:;font-src ‘self’;connect-src ‘self’;media-src ‘self’ /
[ client_ws_0008 ] WOPI::CheckFileInfo returned: {“message":"App is not enabled”}
…
[ client_ws_0008 ] ClientRequestHandler::handleRequest: BadRequestException: Invalid URI or access denied.
In the Nextcloud Log I found the following:
Now I copy & paste the URI to my local browser and give it a try… I was wondering because it seems to work as expected: I got the file information back as associated array.
Next I logged out from Nextcloud on my browser and gave the URI the next try: Now I got the same message back like in the collabora log: Access denied. App is not enabled.
Did you already found anything?
Not sure if the nginx proxy could be the “evil part”…
1 Like
Same issue with my apache here 
Hey,
Nice guide @jospoortvliet everything seems to work exept the editing itself. It gives me some errors about that the private user key is not loaded, logout and in again… just like enableing encryption in Nextcloud.
Altought that just doesn’t do it… Anyone any idea? (image down below)
–restart always doesn’t seem to autostart at boot, had to add it to /etc/rc.local
edit: i found this, we should look into this on failure setting or so.
Find the Docker’s Restart Policies
I’m working on a script to do all this stuff automated, you can help out here: https://gist.github.com/ezraholm50/01e3b1a3b33f329b081e1ed6c632d3ea
When its stable we could implement it somehwere in the repo’s, of which the VM cloud be one…
1 Like
Sorry I can’t answer many questions, this is very new for me too
Anyone who finds a solution for their problem, PLEASE edit your comment or provide a new one with the solution so others can use it!!!
@Pisoko: which version of “Collabora Online” app is installed on your NC? I fixed the issue on my NC installation, but I’m not 100% sure what has been the issue…
I’m seeing a slightly different issue to most people here by the looks of things. My Collabora install which I must admit is a minor deviation from the official line is running into the following curl errors :
Collabora Online unknown error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
Please contact the “https://office.mydomain.com” administrator.
The deviation I speak of is an Nginx Reverse Proxy that I use to make all my different webservices easier to manage in my home. I added a block to my nginx reverse proxy as described in the official documentation for office.mydomain.com changing the 127.0.0.1 references to the IP of the server hosting the Collabora Docker Container. This is also a dedicated standalone server seperate from my NextCloud instance. I also have a seperate dedicated DNS server with all of my A and CNAME records resolving to my Reverse Proxy.
A few things of note that I’ve had a look at, I don’t seem to have any entries in the Nextcloud logs, also the docker logs don’t seem to show anything at all.
If I issue a curl -v https://office.mydomain.com from any of my other linux servers I get the normal response up until the part of the response where I should get the HTML from the nginx welcome screen of the Docker container, instead I get the error listed above. If I issue the same curl -v https://office.mydomain.com from the server hosting the docker container I get the correct response. I believed this initially to be a firewall issue so I’ve disabled the UFW on this server (ubuntu 16.04) but no joy. I get the same errors.
Now I understand that this is not the documented way of configuring Collabora with nextcloud as per the official post but it should still work fine as I have configured a lot of reverse proxy blocks for many different servers.
Could anyone offer me any advise on what could be causing this error.
Regards,
Laoistom
@amilomx I run with 1.1.3 of the richdocuments app.
I am just wondering, since I have a Apache proxy in front of NC and Colabora, would I need to setup websocket proxy for the NC config (on the Apache proxy) so Colabora can use it to connect to NC?
In the docker output I can see a reference to websock back to NC:
wsd-00021-02 00:36:32.028148 [ client_req_hdl ] Request from 192.168.7.241:40259: GET /lool/ws/https://cloud.<mydomain.com>/apps/richdocuments/wopi/files/288560?access_token=NPMKOWnAO5lG5a97vJC8sKPcd1qqDV7Q 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: Mozilla/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: SSrqq5P/ZpDkYinxO6+RxA== / Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits / X-Forwarded-For: 192.168.7.1 / X-Forwarded-Host: office.<mydomain.com> / X-Forwarded-Server: office.<mydomain.com> / Upgrade: WebSocket / Connection: Upgrade
Hey folks, Quick update on my research and testing around my Collobora / Nextcloud issues.
I had installed my NextCloud on Ubuntu 14.04 which it turns out ships with Curl 7.35 by default which doesn’t support SSL. This causes my installation at least to fail as it can’t read the return from the Collobora docker image. I dread the thought but I’m looking at a dist-upgrade of my nextcloud server to 16.04 to hopefully fix my problems.
Wish me luck. I’ll report back regardless of success.
@guidtz and @julio1501 - did you manage to fix your problems with “Invalid URI or access denied”. I have the same problem and cannot find the solution.
OMG DUDE YOU SAVED MY LIFE!!! I LOVE YOU!
So best way is to compile it and everything will work!
As an aside, I ran the docker container under Mac OS X using Docker for Mac and it worked flawlessly on the first try. I wasn’t able to upgrade a linux machine to a new enough kernel to get it working on linux.
The thread is kind of long, so I don’t know if I missed something…
Someone got an “Operation not permitted” link-error like the following fixed?
kit-03388-00 00:57:44.355999 [ loolkit ] link("/opt/collaboraoffice5.1/EULA.odt","/opt/lool/child-roots/3388/lo/EULA.odt") failed. Exiting. (errno: Operation not permitted)
Bernd
Hello there,
I hope this is not a stupid question:
I think I got ahead very far with the installation already. At least when I open
https://office.mydomain.com/hosting/discovery I get a nice XML file with SSL working properly.
However, when I use the office app in nextcloud, I get the following error:
“Collabora Online: SSL certificate is not installed.
Please ask your administrator to add ca-chain.cert.pem to the ownCloud’s ca-bundle.crt, for example “cat /etc/loolwsd/ca-chain.cert.pem >> owncloud/resources/config/ca-bundle.crt” . The exact error message was: cURL error 60: SSL certificate problem: unable to get local issuer certificate”
I have already tried to add all kinds of certificates to the file owncloud/resources/config/ca-bundle.crt, e.g. the ca-chain.cert.pem from GitHub or the SSL certificate I got from StartSSL. However, I cannot get rid of that error message.
In the docker log I don’t see anyting specific for that error.
Any help is highly appreciated!
Kind Regards,
Hans
Hi, I’m having an issue where I get a 404 on https://office.sptmin.com/hosting/discovery
I followed the guide precisely, tried both Ubuntu 16.04 and 14.04, and I can’t seem to locate the error. Any ideas?
@hans: If you installed CODE by docker container on a linux environment you must get the self signed certificate generated inside the docker:
-
check what is your docker id ( inside the list you should find the collabora/code)
sudo docker ps -
run a bash in your docker ( I guess other methods are possible but this should do)
sudo docker exec -i -t /bin/bash -
You can find the key here:
cat /etc/loolwsd/ca-chain.cert.pem file
then copy this key using a safe method on your nextcloud and add it at the very end of the nextcloud trusted keys file:
for ubuntu-like: /var/www//resources/config/ca-bundle.crt
@rolandixor: I had the same issue than you, I forgot the part where I had to redirect all the ressources on the environment where the CODE docker is deployed
Double check your nginx/apache settings,
for apache: in your /etc/apache2/sites-enabled your -ssl.conf should contain:
WOPI discovery URL
ProxyPass /hosting/discovery https://localhost:9980/hosting/discovery
ProxyPassReverse /hosting/discovery https://localhost:9980/hosting/discovery
Don’t forget to enable the conf with a2ensite and service apache restart
Hope this helps
I am having the same issue with the certificate error. I have although copied the correct CA as per your instructions already but still perl error 60 for certificate.
I am hosting the environment on a seperate box , so seperate box for nextcloud and seperate for docket collabora online
/hosting/disovery works , I can open the lool plugin manually defined within the xml but from the app its error