Hello,
I’m trying to set up LibreOffice Online. I tried a plethora of combinations (even tried to compile loolwsd on my own), but neither of them worked, whatever I do, loolwsd comes up with another kind of error phenomenons, it’s almost ridiculous how nothing can get it to work and how many creative ways can it fail.
My actual error is similar to what others have already mentioned: when I try to edit a document, I get „We are sorry, this is an unexpected connection error. Please try again.”.
Docker has been started like this:
docker run -t -d -p 192.168.1.155:9980:9980 -e “domain=xenial” --cap-add MKNOD collabora/code
Domain: I tried to substitute my ownCloud instance’s name there, that didn’t work, and now it is loolwsd’s internal hostname. I’m not entirely sure what domain should be written there. What I’ve tried:
– public domain name of my ownCloud (let’s call it cloud.mydomain.tld);
– private domain name of the ownCloud host (ownCloud.lan);
– now it is “xenial” / “xenial.lan”, which is the host where loolwsd is running.
As I said, neither of these worked.
The docker output shows these lines:
wsd-00021-05 00:02:30.064425 [ client_ws_0004 ] WOPI host is not on the same host as the WOPI client: “X.X.X.X”. Connection is not allowed.
wsd-00021-05 00:02:30.064460 [ client_ws_0004 ] No acceptable WOPI hosts found matching the target host [cloud.mydomain.tld] in config.
wsd-00021-05 00:02:30.299793 [ client_ws_0004 ] ClientRequestHandler::handleRequest: BadRequestException: Invalid URI or access denied.
(I quoted only the lines I find suspicious. If you need the rest, ask away.)
X.X.X.X is my public IP address, I actually have no Idea why I see it there since both ownCloud and loolwsd should only see private IPs. Maybe it resolves cloud.mydomain.tld?
To be honest, I am really confused what should communicate with what on which ports. At first I thought ownCloud clients don’t need to connect the loolwsd server directly, but meanwhile it turned out it’s necessary. It would help a lot to have a diagram or something to see how it all should assemble together. Since currently there is no way to access loolwsd from the Internet, I at least would like to see it work on my private network.
I try to explain how the current setup looks like: I have a reverse proxy which accepts connections from the Internet on a public IP and forwards HTTP traffic to ownCloud.lan (which is a private host on my LAN, has no public IPv4 address). The reverse proxy also performs SSL offloading, thus connections are only encrypted until the proxy, and there is no encryption between the reverse proxy and ownCloud. Then there is xenial.lan which is basically a drop-away test VM, for now I want to set up LOOL on that. The loolwsd currently runs in docker, and as the tutorial suggested, I set up a reverse proxy for it, even though I don’t fully understand the proxy’s supposed role here. This proxy runs on xenial, and it IS NOT the same reverse proxy that is bridging connections from the Internet to ownCloud.lan, but it is very likely that I will set up my Internet-facing reverse proxy to forward connections to loolwsd too.
Any insights are welcome, thanks in advance.
~ MegaBrutal
P.S.: Yeah, I know it’s a Nextcloud forum, but I really don’t think is that ownCloud is the problem here. I’m thinking on adopting Nextcloud though.