WRN client - server version mismatch, disabling browser cache
It somehow seems to be a cached JS talking to an upgraded WSD… hm could you try in a anonymous window or by clearing the web browser cache and report back
Hi m8 and thank you for the quick reply.
I’ve been trying to solve this problem for a long time.
I first installed coolwsd in unprivileged lxc. Then I tried privileged lxc and finally KVM. I always get the same mistake.
Installation procedure
I’m confused about all the threads, there’s this, and also this:
But I see no symptoms in either topic that in what way CODE isn’t working, or isn’t accessible from Nextcloud.
The admin console isn’t particularly necessary to get it to work. However, the reverse proxy config seems incomplete, if you have one, and the CODE server isn’t accessible from outside, you should set up something similar to what’s described here: Proxy settings — SDK https://sdk.collaboraonline.com/ documentation
I also wrote on the nextcloud forum, but they didn’t advise me. Please read the topic there as well.
I want to integrate collabor online into nextcloud. If I want to integrate it into nextcloud, collabor online must work in LAN.
This is my situation:
Have you checked the reverse proxy configuration I suggested? That’d be necessary. You may have to adapt it a bit if you are going for a terminating or a pure http setup (in the latter case NC has to be on http as well… it really should only be used for testing purposes).
What you could check when troubleshooting:
open https://<CODE server host + port if not the default>/hosting/discovery in a browser,
check if the host in the URL is the same as the <CODE server host + port if not the default>, if not, you may have to edit server_name in /etc/coolwsd/coolwsd.xml,
open one of those URLs in the browser, it should open a blank CODE UI with some error message (that’s fine), if you get to this point, CODE should be accessible from NC,
if you still get some blank screen when opening a file in NC, check the browser console for error messages like CSP violation.
connected to my previous post, I had the same issue.
After following the instructions on the webpage: server_name in /etc/coolwsd/coolwsd.xml and reverse proxy with nginx webserver, things worked OK.
The only change to the locations I had to make was to change
proxy_pass https://<intern_ip>:
to
proxy_pass http://<intern_ip>:
=> can someone explain why this could be and what the impact if this change is?
I’ve gotten a little further, but I still can’t open the documents in the nextcloud. I have installed a new container LXC 192.168.1.110 (debian 11 netinst), which will be designed for collabora.
Installation procedure
If I enter the web browser url 192.168.1.110:9980 the result is OK
If I enter the web browser url http://192.168.1.110:9980/browser/dist/admin/admin.html the result is
to be honest - guessing now: did you add your server name to all coolwsd.xml files and does the domain-env in the colalbora setup point to the nc-server?
<storage desc="Backend storage">
<filesystem allow="false"/>
<wopi allow="true" desc="Allow/deny wopi storage.">
<host allow="true" desc="Regex pattern of hostname to allow or deny.">nextcloud.example.com</host>
<host allow="true" desc="Regex pattern of hostname to allow or deny.">10\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}</host>
<host allow="true" desc="Regex pattern of hostname to allow or deny.">172\.1[6789]\.[0-9]{1,3}\.[0-9]{1,3}</host>
etc...
of course example.com I replaced my original domain.
OK - I did not modify this part at all - I was referring to the <server_name< setting mentioned in the intructions:
<server_name desc="External hostname:port of the server running coolwsd. If empty, it's derived from the request (please set it if this doesn't work). May be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default=""></server_name>
<server_name default="collabora.example.com" desc="External hostname:port of the server running coolwsd. If empty, it's derived from the request (please set it if this doesn't work). May be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string"/>
resp
<server_name desc="External hostname:port of the server running coolwsd. If empty, it's derived from the request (please set it if this doesn't work). May be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default="">collabora.example.com</serv>
Would you be able to provide me with the config file coolwsd.xml and the server block from the reverse proxy?
What exactly did you change in config files?
