I saw a similar reddit post about this with no answers and I was hoping folks over here might have some answers. I’ve been trying to get a stand alone collabora server working to use in nextcloud. My nginx proxy manager config works as my nextcloud server can ping the collabora server fine and when I enter the URL I get a page that says “OK” but I cannot access the admin panel without this error message. I thought it might be an ACL issue so I cracked it open only to find the recommended UID conflicts with “user_apt” which obviously I don’t want to mess with.
Please let me know if you have any insight as i’m excited to use my taco bell font as blazing fast speeds with this server running correctly.
To clarify, when input the domain I get a simple html page that says “OK” when I input the IP:port I get the afformentioned error and no ability to manage the collabora server.
In nextcloud I believe it says the server is working and then when I go to edit a document it simply doesn’t open.
Hmm that is interesting. Do the container logs for collabora give you any output? (Click the application, in the container list there is an icon for logs for each container in an app)
It seems like the nextcloud server is able to reach the collabora server. I don’t know how much checking it does beyond just pinging the server. So that doesn’t necessarily mean that it is working.
I noticed this issue last week or so. Worked fine on June 8th but now I can’t use the Collabora web UI and when I try to open a document in Nextcloud it just hangs forever. Was there a borked update or something?
It seems like the nextcloud server is able to reach the collabora server.
If that’s the case for OP, then I might be having a different error with the same result, since I don’t know how Nextcloud could be reaching a server that only spasms to life for a few seconds with repeated kicking.
Alright, I’m not sure why it wouldn’t work before, but I’ve got the built-in CODE server working now.
I was able to get the separate Collabora server to run by editing the app and setting the Server Name to the machine’s IP address rather than collabora.mydomain.com.
Nextcloud would only connect to it if I disabled HTTPS, and after adding 192.168.0.0/16,172.16.0.0/12,10.0.0.0/8 as authorized WOPI hosts, it threw another socket error when I tried to open a document:
Failed to establish socket connection or socket connection closed unexpectedly. The reverse proxy might be misconfigured, please contact the administrator.
If there’s an easy way to fix this, I’m all ears, but otherwise I’m gonna say the built-in CODE server works well enough.
Hey sorry to fall off with this post, after moving house and updating nextcloud and collabora to the latest and greatest everything works flawlessly and better then ever so I’m pretty sure the updates had something to do with it! Happy hosting folks.
