I followed @icewind s guide for configuring collabora on nginx, but when attempting to load a new or existing file in Collabora Office I receive the following error:
For the docker installation I am using the same SSL domain that nextcloud is currently configured on.
I added the suggested location entries to the pre-existing nginx config.
After installing the app I set the online server to https:// my. domain. com. I tried adding :443 to the end and get the same message. I tried :9980 and received the > cURL error 7 message @offerlam received.
I assume that means that I’m setting the online server appropriately.
Only error in the log is Undefined index: dir at /var/www/apps/richdocuments/controller/documentcontroller.php#289
I had the problem that my nextcloud server was behind a edge firewall. I hadn’t NATed the ports 9980 to my nextcloud - only 443 since thats uses for the clients and web access…
if you nextcloud server is not directly exposed to the internet, check that you are natting aswell… also make sure if you have a local firewall on the server, that its not blocking anything…
could you also post you .conf file for the webserver?
@offerlam after reading through your issue I port forwarded 9980 to be safe. Same thing. I never configured a firewall, so I don’t imagine that being the issue.
If it means anything, I’m running of an ARM based Rasperry Pi. I didn’t receive any error when configuring the docker installation.
but when im compare yours to mine mine is different in the servername… you servername is my.domain.net which i assume is your nextcloud domain name… i use the office domain you have to create. so my servername is office.dingit.dk not data.dingit.dk
Okay, I’ll try running the process over again but with a different servername. The nginx directions I followed seemed to suggest that it could be done either way, though. Any thoughts @icewind?
standard_init_linux.go:175: exec user process caused “exec format error”
I’m thinking that this is an issue with the Raspberry Pi’s ARM processor… The container isn’t even runnning. Damn. Possible to run outside of docker maybe?
The installation of collabora is vary difficult in my perspektive. which is also why they made the docker solution. so ofcause you can get collabora working on nextcloud not using docker. Its just hard… not something i know anything about
I think the problem is the arm architecture. The docker image is build for the x86 architecture and can’t run on a arm processor. Also copying everything out of the docker container wouldn’t help, it is still the wrong processor architecture. Only compiling everything for arm could help.
I think a found some lead. Collabora/code docker container is crashing since the STATUS uptime is always less than a second up and then it the up time resets to Up 1 seconds…
sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ff7bb05494f4 collabora/code "/bin/sh -c 'bash ..." 12 hours ago Up 34 seconds 127.0.0.1:9980->9980/tcp peaceful_haibt
5a0be9cc3e04 mquandalle/wekan "/bin/sh -c 'bash ..." 14 months ago Up 2 months 0.0.0.0:8081->80/tcp wekan_wekan_1
02cf142a5f3c mongo "/entrypoint.sh mo..." 14 months ago Up 2 months 27017/tcp wekan_wekandb_1
I’m using Docker version 17.05.0-ce.
In my case I think it’s not related to wrong Nginx configuration, but more about a instable docker image of collabora. If I join the container (docker exec -i -t ff7bb05494f4 /bin/bash). I will get kicked-out after some seconds because it’s crashing