Nextcloud and collabora integration

ℹ️ Support 📄 Collabora
1

I have a big problem that I cannot solve about Nextcloud and Collabora integration.

I don’t even know if it is a Nextcloud-related problem or a Collabora pb.
But for me, Collabora is impossible to use.
Here it is.

Say we have a nextcloud Docker container and a Collabora Docker container.

Nextcloud (cloud.example.com) is behind a reverse-proxy as is the coll.example.com which is Collabora behind the same Nginx.

Independently each works well.

In the Nextcloud administrator interface for Collabora I typed as link to the Collabora service:
https://coll.example.com (and the light is green).

In the docker-compose.yml for Collabora here is an extract:
- domain=cloud.example.com
- server_name=https:\/\/coll.example.com
- net.proto=IPv4
- ssl.enable=false
- ssl.termination=false
- username=admin
- password=

BTW, none of net.proto, ssl.enable, ssl.termination works!
Those have to be set up after the starting of the container via a

docker cp loolwsd.xml

If I do not put \ before / collabora doesn’t start invoking a error on line 1 col 0 for loolwsd.xml.
Well, finaly I have the correct loolwsd.xml set as you see thereafter:

<server_name desc="External hostname:port of the server running loolwsd. If empty, it's derived from the request (please set it if this doesn't work). Must be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default="">https://coll.example.com</server_name>

OK?

Well, so the link between Nextcloud and Collabora cannot work because of a stupid http: that something inserts BEFORE the correct url. Is this Nextcloud, is this the Collabora plugin for Nextcloud or is this Collabora itself?

Content Security Policy: The page's settings blocked the loading of a resource at [http://https//coll.example.com/loleaflet/a5d14f2/loleaflet.htm…qn5i552&title=tt.odt&lang=fr&closebutton=1&revisionhistory=1](http://https//coll.blas.info/loleaflet/a5d14f2/loleaflet.html?WOPISrc=https%3A%2F%2Fcloud.example.com%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F4553_occhcqn5i552&title=tt.odt&lang=fr&closebutton=1&revisionhistory=1) ("form-action").

Where does this http:// come from?

And why https doesn’t have the : any more?

Answer if you can but I’m fed up with this kind of bullshit.

Thank you,

db

2

If you are trying to run collabora using http only, why is your servername https? Your servername should not include any http or https declaration.

3 
  - domain=coll\\.example\\.com

grafik
grafik1289Ă—88 12.7 KB

@dblas any reason why you use an extra domain for collabora? is the conatiner running on another server/host?

which nextcloud container are you using? (apache or fpm)

4

Thank you for your interest kevdog.
Https is needed since collabora is behind a reverse proxy that does https.

Here is complement information: what the javascript console displays when I try to open an .odt file:

The source list for Content Security Policy directive 'frame-src' contains an invalid source: 'http://https://coll.example.com'. It will be ignored.
VM1043 index:1 The source list for Content Security Policy directive 'form-action' contains an invalid source: 'http://https://coll.example.com'. It will be ignored.

And, above all:

jquery.js:4383 Refused to send form data to 'http://https//coll.example.com/loleaflet/a5d14f2/loleaflet.html?WOPISrc=https%3A%2F%2Fcloud.example.com%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F7_occhcqn5i552&title=Example.odt&lang=fr&closebutton=1&revisionhistory=1' because it violates the following Content Security Policy directive: "form-action 'self' http://https://coll.example.com".

You can notice 3 things:

  1. the colon from https disappeared. Why?
  2. the URL is prefixed with an http which I don’t know where it comes from.
  3. Moreover what is this Content-Security-Policy directive knowing that the reverse proxy doesn’t have one. I disabled it to be sure.
    I think that 3 is the result from 1 and 2. Of course something like http://https// doesn’t look alike an URL.

If you have any idea …
db