I’m following the guide at https://nextcloud.com/collaboraonline/ and I have a fresh NextCloud installation version 9.0.52 on Ubuntu 14.04. There are several problems:
Special characters when running docker: the documentation mentions the need to escape periods. Are there other characters (e.g. hyphens) that should also be escaped?
Apache Configuration ServerName: the guide mentions the servername including the colon and port but my understanding is that the server name should be without the port, isn’t it?
Apache Configuration DocRoot: the virtual host declares some paths that will be handled by the proxy settings, but if you browser to the domain itself, Apache is serving that request without using any proxy and in the default configuration delivers the request as if it were going to the default docroot of that host. Shouldn’t there be a DocRoot declaration that captures everything not being handled by the proxies and respond with a 404?
Install the “Collabora Online app”: The problem is that the app in my installation is named “Collabora Online Connector” and it is labeled as experimental. Is that correct? If not, why is my installation which is fresh (see above) not showing the correct one?
When going to the admin area where I want to provide the URL for the Collabora instance, I can click on “Save” but it doesn’t do anything. Nothing found in the logs for this. Maybe this is because of the previous item and I’m running the wrong app version? The version number given is 1.1.3
Any help is much appreciated and maybe we should eventually update the installation guide.
While I can’t say anything about 1. to 3. for my test setup, I ran into the same questions you describe in 4. and 5.
For me, the “Save” button didn’t work either when I tried with Safari – the field simply reset to the default entry (localhost) after exiting the settings. However, it did work when using Firefox on the same Mac.
I can now open Collabora from the Nextcloud dropdown menu and select one of my ODT files, afterwards it loads some kind of UI (with text formatting options), but loading the document fails with an “unexpected connection error”.
Please check your browser console log. Also what browser do you use?
This rather indicates a configuration issue, please post detailled what you did as well as the log output of the docker container. (start it without -d so we can see what it fails at)
Thanks @LukasReschke I’ll address 1-3 accordingly and I can already confirm that I now have an app “Office” in the drop-down which I can open and that then gets me to https://cloud.my-domain.com/index.php/apps/richdocuments/index with 4 buttons to add three different document types or to upload one. So item 4 and 5 is now also resolved.
However, when I click on “New document” I get a gray square and when I click on that I get a message “Failed to open undefined, file not supported.”
This is a permission problem on your environment. Please make sure you don’t have anything in place that restricts the permission of the container. One example is AppArmor, it may be sensible to disable AppArmor for the docker container.
… if somebody has some decent knowledge about AppArmor then feedback on proper rules for Ubuntu are welcome
Aso make sure your Docker version supports already dropping the capabilities, alternatively starting with --privileged may help as well. On my Ubuntu Xenial docker host it was however sufficient to disable AppArmor.
I don’t think a docker container should rely on a disabled apparmor environment. Docker already provides a default policy.
If this is not sufficent you can provide your own policy. Disabling apparmor entirely might make an server more vulnerable.
If this is still an issue this weekend, i will setup a VM and test it with AppArmor disabled
Tried using firefox for entering the domain of the Collabora VirtualHost right after reading your note - but to no avail.
The browser console doesn’t say a thing for me - except for several errors about certificate issues. But hitting the SAVE button doesn’t do anything at all, so I wonder if I’m using it correctly (I’m unfamiliar with it, I’m not a developer) - I just opened it and then hit the button again.
The last two kit-… lines (about link…failed) are bold red
This keeps on happening, even when I don’t have “Office” open.
The browser debug console shows error: Service is unavailable. Please try again later and report to your administrator if the issue persists. from the websocket connection:
For anyone having issues where the save button is not working - I got it to work just by waiting a couple of seconds; looks like it’s really slow. Also there’s no confirmation of it having saved the new URL.
Also I received a cURL error saying that the root certificate had not been installed - I concatenated my self signed CA cert onto ca-bundle.crt and that’s fixed it. I use self signed certificates and have CloudFlare on top in order to present a trusted cert. The ca-bundle.crt is going to get overwritten with every update, is there a better way of doing this? I don’t really understand either because my CA is trusted on my server and I can use cURL via the shell against it.
One last thing - is the docker container self updating?
I was able to set the URL using the following against my database:
insert into oc_appconfig(appid, configkey, configvalue) values ('richdocuments','wopi_url','https://[your url here]');
Now I can open the page that shows the document list. When I open a document, I’m now also getting the We are sorry, this is an unexpected connection error. message.
I’ve disabled apparmor and running in --privileged mode.
Are you all on Ubuntu 14.04? My best guess is https://github.com/docker/docker/issues/20658 then: Probably the kernel isn’t compiled with CONFIG_AUFS_XATTR. Has anybody the chance here to test that quickly?
I have quickly tested to run docker with the --security-opt=seccomp:unconfined option and it looks as if it is working much better now. Still having to sort out my firewall issue but when I turn that off, it looks as if it is working OK.
