Still the same, opening file gives ony turning wheel…
Collabora docker running. I can get to the
https://office.domain.com:9878/hosting/discovery which gives me an xml
I observed the apache log /var/log/apache2/other_vhosts_access.log and clicked the ods files then…
From there I got an axample entry:
office.domain.com:9878 192.168.30.1 - - [07/Jan/2019:11:52:11 +0000] "POST /loleaflet/173510f/loleaflet.html?WOPISrc=https%3A%2F%2Fdomain.com%3A9878%2Fnc%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F2011_oc6z4ethoujb&title=test.odt&lang=en&closebutton=1&revisionhistory=1 HTTP/1.1" 200 2941 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0"
I tried to open that loleaflet link directly entering this into browser:
https://office.domain.com:9878/loleaflet/173510f/loleaflet.html?WOPISrc=https%3A%2F%2Fdomain.com%3A9878%2Fnc%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F2011_oc6z4ethoujb&title=test.odt&lang=en&closebutton=1&revisionhistory=1
which gives the Collabora online editing window but again a turning wheel
Apache virtualhosts are definitely set up properly, both having ssl certs attached…
I can only think of the non-standard port 9878 I am using…
Here I found another solved issue where the user apparently solved with switching back to standard 443:
Can I somehow check if Nextcloud or Collabora have access to files? The WOPI storage?
My docker is set up to use
Storage Driver: devicemapper
Shall i switch to another?
UPDATE
Ok, unfortunately no time for playing hide and seek with this buggy…
I went back to image 3.4.2.1 from
https://hub.docker.com/r/collabora/code/tags
with
docker pull collabora/code:3.4.2.1
I am back online with my setup and can edit docs…
Maybe I will try another image later 