Actually this should not be a game trying to guess the right options.
I expect a documented way of getting this to work.
Besides that, what should I expect from a solution that works for some users and does not for others?
I don’t really think that - especially in my case - this is a configuration issue.
Otherwise it wouldn’t work for any user…
And it’s about how this solution is being pushed. Nowhere does it say this is an alpha version that may work if you’re lucky.
Not on this page: https://nextcloud.com/collaboraonline/
and not on this one either:
It even calls this version 2.0.
Which to me sounds like the worst bugs should be fixed.
Maybe some of the problems come from the Collabora Office Docker Toy being intentionally crippled so that only x users may be able to use it or one may only open y documents?
I can understand that Collabora wants to earn money with their work.
But there is not even a declaration on where the limits are set.
I’m not getting the ‘Well this is embarrassing’ message any more.
After the update as of today, I’m in fact not getting anything anymore.
If I click on an office document, all I get is a grey background.
This is all very discouraging.
My guess it has to do with these stupid limitations put into collabora office.
Of course we have several hundred users on our Nextcloud.
But if there is exactly one of them (me) trying to use Collabora Office, I think it has to work.
Or do these limitations apply to the number of users in the Nexcloud instance?
If more than ten then don’t work or something?
It might be the DNS of the container as many don’t think of it as a client, I didn’t anyway
Docker just copies the resolv.conf of the host and with internal installs sometimes that just does not work
But some stuff to check and post, Nextcloud do, do support… But can run you through some stuff.
To check the DNS/Certs entry. nslookup subdomain.example.com openssl s_client -connect subdomain.example.com:443
Check from clients, server and container.
Docker, wasn’t very keen at first but actually become to like it. docker ps -a#list all containers. docker stop [container-id]#stop container docker rm [container-id]#delete container docker images#list all images docker rmi [image-id]#delete image docker exec -i -t [container-id] /bin/sh#run shell inside container docker logs [container-id]#view log docker info#environment setup
Docker info is a good place to start as it will also give distro and backend storage details as there is much variance in distro aufs support, post results here.
docker exec -i -t [container-id] /bin/sh allows you to enter a root shell in the container and you can install software such as dnsutils or nano to check things out and edit.
If you are behind a subnet DNS then docker run -t -d -p 127.0.0.1:9980:9980 -e 'domain=nextcloud\.vote4u\.org\.uk' --dns=192.168.1.2 --restart always --cap-add MKNOD collabora/code
with --dns=192.168.1.2 making sure the container is pointing correctly at the right DNS server.
If its aufs that is the problem like on Debian or Ubuntu if sudo apt-get install -y --no-install-recommends
Hasn’t been run device-mapper does.
Might be aufs and an easy way is to swap to device-mapper instead.
Docker info will show Storage Driver: aufs and it doesn’t work and we can change to devicemapper
grep ExecStart /lib/systemd/system/docker.service
will return something like the below which we need to place in a system.d conf file ExecStart=/usr/bin/dockerd -H fd://
Create like so (paste):
ExecStart=/usr/bin/dockerd --storage-driver=devicemapper -H fd://
Dunno why it has a first blank ExecStart= but I copied it verbatim and it works.
While i was doing my collabora installation I also had the unauthorized WOPI host and i came to the conclusion that this error is due to inserting the wrong hostname into the sudo letsencrypt certonly --webroot --email your-email-address -d office.your-domain.com -w /usr/share/nginx/office/ command, so double check you have written the url of your Nextcloud server correctly.
Furthermore, i have collabora and nextcloud setup in two different ubuntu server, since i experienced alot of latency when i had both in the same ubuntu server.
Finally, i think your nigix config should look like this;