Onlyoffice vs Collabora in Nextcloud
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
No you don't. That's not true at all.
Yes you can create an app that uses a syscall that may be deprecated or uses a very new kernel hook that isn't available in older kernels. So you would be limited to kernels that support those, but it is in no way a requirement to have the exact same kernel and certainly not the exact same OS.
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
I've literally never had it happen and I use it all of the time. Build on Fedora, deploy to either RHEL/CentOS or Fedora. And pull images from Ubuntu and use those all of the time.
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Last time I looked at them, the Collabora open source version needed compiled.
It's never needed that as long as I've known about it. It's a Docker instance, which is the real pain of it.
Hrm, I'll have to take another look. Docker would make it somewhat easier.
No, makes it ridiculously harder.
The Collabora documentation is really straightforward on the container and looks very easy. What isn't "production" about the setup?
With Docker, you have to be running the exact same version of OS and kernel that the devs who built the container. Docker specifically isn't portable like so many people claim.
No you don't. That's not true at all.
Yes you can create an app that uses a syscall that may be deprecated or uses a very new kernel hook that isn't available in older kernels. So you would be limited to kernels that support those, but it is in no way a requirement to have the exact same kernel and certainly not the exact same OS.
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Any examples of what broke in what apps on what distros?
-
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
-
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
Oh, if that's what he means by portable. Yeah you don't put an image on a system and move it to another. You just spin up the image on another system.
-
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
Oh, if that's what he means by portable. Yeah you don't put an image on a system and move it to another. You just spin up the image on another system.
I have no idea what he thinks he means. But I do know he is spewing bullshit.
-
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
Oh, if that's what he means by portable. Yeah you don't put an image on a system and move it to another. You just spin up the image on another system.
I have no idea what he thinks he means. But I do know he is spewing bullshit.
docker pull imagestart it up, doesn't work. Could be things have changed since I've tried, hasn't been that long tho. -
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates said in Onlyoffice vs Collabora in Nextcloud:
@JaredBusch said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, that's what everyone claims, but I have very rarely had a Docker container work when deployed to a different distribution that it was created on, and sometimes even different kernel versions break things.
You are wrong. See my own guide, here in the community, to installing the Ubiquiti UNMS controller on Debian.
@travisdh1 said in Onlyoffice vs Collabora in Nextcloud:
Yes, they are supposed to be portable, but every distribution has a slightly different compiled kernel. Because the kernel is shared, random things are just broken and/or don't work. I've seen it happen so often that I just assume anyone claiming Docker containers works with it in a monolithic environment. In which case, of course they just work.
Docker containers are not portable once installed. They are not designed to be moved around. Stop saying shit and give real examples.
Oh, if that's what he means by portable. Yeah you don't put an image on a system and move it to another. You just spin up the image on another system.
I have no idea what he thinks he means. But I do know he is spewing bullshit.
docker pull imagestart it up, doesn't work. Could be things have changed since I've tried, hasn't been that long tho.That could be so many things. Why would you default to thinking it's the kernel?
-
Decided to go with OnlyOffice and have it running. Both servers are behind nginx and https. It adds the menus in NC to create/edit docs but returns a normal NC page that has a white body. Seems like the majority of people use docker but I have OO running on a CentOS7 vm. Has anyone got this to work successfully? Both pieces are working but not together. Frustrated to say the least......
On the plus side... I found and corrected an issue with my nginx config on NC. -
@travisdh1 You are not alone. I have spent more hours on this than I'd like to admit. Still cannot get it to work. I have read every document I can find. Each solution I find makes no difference.
Has anybody been able to get this to work with NC and OnlyOffice behind nginx?
-
@brandon220 said in Onlyoffice vs Collabora in Nextcloud:
Has anybody been able to get this to work with NC and OnlyOffice behind nginx?
Not with OO, but @romo managed to finally get it working with Collabora. Likely the issues are the same.
-
@scottalanmiller I'm pretty close to throwing in the towel. Their preferred method is fine for those running Docker, but I prefer using VMs and behind Nginx. I don't see why OO wants the certs to be installed manually, etc.
-
@brandon220 said in Onlyoffice vs Collabora in Nextcloud:
@scottalanmiller I'm pretty close to throwing in the towel. Their preferred method is fine for those running Docker, but I prefer using VMs and behind Nginx. I don't see why OO wants the certs to be installed manually, etc.
We tried it with Docker, it didn't work there either.
-
@scottalanmiller Funny thing is that it has an almost 5-star review in the apps section in NC..... I'd like to see how many people actually get it to work.
-
@brandon220 said in Onlyoffice vs Collabora in Nextcloud:
@travisdh1 You are not alone. I have spent more hours on this than I'd like to admit. Still cannot get it to work. I have read every document I can find. Each solution I find makes no difference.
Has anybody been able to get this to work with NC and OnlyOffice behind nginx?
If I get a chance tonight I'll give it a shot.
-
@stacksofplates Did you have any luck?
-
@brandon220 said in Onlyoffice vs Collabora in Nextcloud:
@stacksofplates Did you have any luck?
Sorry I haven't had time. I'll make sure I do it tonight.
-
@stacksofplates I'm going to work at it more too. It seems like I'm so close to having it functional. I know it is because of nginx.
-
Ok so it looks like Collabora isn't that great. It seems like everyone has issues from it (looking at their site) and it looks like OnlyOffice might be the better option (from the posts on the Collabora site). I got them to talk to each other in the same pod, but I get cryptic log messages.
I get this message
along with these log messages:wsd-00029-00085 2019-06-19 22:06:44.514243 [ docbroker_007 ] WRN Client session [0011] not found to forward message: o84 signaturestatus: 0| wsd/DocumentBroker.cpp:1798 wsd-00029-00030 2019-06-19 22:11:54.640649 [ prisoner_poll ] WRN ForKit not responsive for 5284 ms forking 1 children. Resetting.| wsd/LOOLWSD.cpp:427 wsd-00029-00089 2019-06-19 22:12:07.144677 [ docbroker_008 ] ERR #20: Wrote outgoing data -1 bytes. (EPIPE: Broken pipe)| ./net/Socket.hpp:1058 wsd-00029-00089 2019-06-19 22:12:07.145078 [ docbroker_008 ] WRN Client session [0013] not found to forward message: o96 signaturestatus: 0| wsd/DocumentBroker.cpp:1798 wsd-00029-00099 2019-06-19 22:12:17.482320 [ docbroker_009 ] ERR #25: Wrote outgoing data -1 bytes. (EPIPE: Broken pipe)| ./net/Socket.hpp:1058 wsd-00029-00099 2019-06-19 22:12:17.482704 [ docbroker_009 ] WRN Client session [0014] not found to forward message: o108 signaturestatus: 0| wsd/DocumentBroker.cpp:1798 -
Just for kicks here's what I set up:
pod
podman pod create -p 8080:80 -p 9980:9980 --name nextcloud-podNextcloud
podman run --pod nextcloud-pod -d nextcloudCollabora
podman run -d -t --name collabora --pod nextcloud-pod -e "extra_params=--o:ssl.enable=false" -e "domain=example\\.com" collabora/codeThen I just pointed the Collabora app in Nextcloud to http://127.0.0.1:9980.
-
I've decided to go with OO because of its strong use of native MS Office file formats. I have Nextcloud, nginx, and onlyoffice all running as VMs and both NC and OO have certs and can be accessed via https. NC can connect to OO fine and I can generate a new document in NC - however, the document opens as a blank page and throws an error inside the webpage if you look at the logs. I am sure that it is a problem with the .conf file in nginx but I haven't been able to narrow it down. I think it has something to do with connecting to the OO server as http behind the proxy. Most of the documentation shows using certs directly on the OO server but that defeats the purpose of my proxy.
