The problem is I can’t open any documents, I just get the error “Well, this is embarrassing, we cannot connect to your document. Please try again.”
Can anybody please help me fix this and help diagnose what the problem is?
Let’s summarize what we already now on a quick list.
Proxy
** Are you using 2 (sub)/domains, one for Nextcloud another for CODE?
** Did you copy paste the reverse proxy configuration from here changing only domain name and SSL paths?
Web Server
** What web server are you using? (I recommend Apache for this setup)
SSL
** Do you own a valid SSL cert, or are you getting it by using Let’s Encrypt?
Docker
** (I believe you have aufs support)
** Are you running the domain name of your Nextcloud with backslashes (\) as shown here.
Hi thanks but my Nextcloud setup is already in production and being used by quite a few users. I’d rather if there is a way we can debug what is wrong with my current setup please?
Hi @Asif_Khan !
In order to get help, you need to share more information than that.
Please use the installation guide to check that every point has been meet (and show here the output).
You can use this or this one.
That way it’s more likely for other users to help you, me included.
Cheers!
Hi just to update that my implementation IS now working just simply through Ubuntu fixing something, a package update etc with docker. I haven’t adjusted anything, rather just rechecked and retried things a few months later and now the documents load up great.
Periodically documents just won’t open. The only pattern I’ve noticed so far (due to not being to test too much on a production machine as yet) is that if I’ve had to restart bind or apache or something on the server - then if I log into Nextcloud and try edit a document I get that nasty error “Well, this is embarrassing, we cannot connect to your document. Please try again.”
After a full reboot of the server documents open again. It’s pretty frustrating. What is the correct procedure when managing your server day to day to make sure Collabora keeps working too? Is this a bug or normal behaviour, and is there a workaround such a script or something that can keep it “alive”?
The issue was DNS resolution inside the docker container that ran collabora. The DNS for my nextcloud domain was resolving to the public address, which is not reachable from the container or the nextcloud VM which had the container running in it. I connected to the docker instance, and added a line in the local hosts file that pointed back to my nextcloud VM’s docker address as follows. At that point the documents can be viewed/edited without issues.
Nextcloud VM’s docker IP address is 172.17.0.1.
I connected to the container instance as:
docker container ls (shows the active container list) docker exec -i -t /bin/sh (replace with the found container id)
Once in the shell, run the command
echo “172.17.0.1 nextcloud.mydomain.com” >> /etc/hosts
Spoke too soon. It worked for a couple of new documents that I created and now doesn’t work again. Can’t imagine what is so hard about this integration. Pretty standard ubuntu 16.04 image for nextcloud and running the collabra configuration from the single script install as most people have done here.
@jayanm Thanks for the solution.
You can provide --add-host to the container when starting it to edit the containers /etc/hosts file.
This way it is reboot persistent.