_BEST_ Download Collabora
Galina Thurby
Collabora's initial focus was instant messaging (IM), Voice over IP (VoIP) and videoconferencing technologies, but the company has since expanded its offering to include general multimedia, mobile web technologies, collaboration infrastructure, automotive infotainment platforms, graphics optimization, multimedia interoperability & productivity software. Collabora's department Collabora Productivity is the main developers of LibreOffice.[3][4][5][6]
Hi.
I installed a fresh instance of the latest nextcloud today. Everything worked fine. I connected to the external base. However, when I exposed the traffic to the world via loadbalancer, the page loads endlessly. This is an internal network. I would like to add that previously I installed different versions and always after installing the collabora add-on and connecting to the world the site was impossible to use. It was able to load for 10 minutes. Can anyone help me solve this problem?
I tried to test collabora and the result was the same, unusable due the poor performance. Did a lot of changes in the config but no success, if you solve the problem please share, would be fine to take a look to collabora.
The installation runs smoothly but as soon as i hit the cummunity package button for installation that also installs collabora the whole nextcloud instance becomes unresponsive and so slow you would think it is dead.
As of 11/4/22 the collabora docker crashes and burns in unraid. You manually start it. It stops a few seconds later. No config file will fix this. I went to UNRAID forums and cannot find a reference to collabora and CHVB in the same sentence. Does that mean it is abandoned?
I changed the domain to blank as suggested above to successfully start the collabora container and now nextcloud is working again. I guess it must be how I configured nextcloud to connect to collabora or swag is doing something weird
Had the issue of not being able to open anything and the web ui not working. Made the associated changes for the nginx in my swag container, deleted collabora container and image, reinstalled from the app store (no domain needed as it's now setup as "first come, first serve" and bam... documents are opening again.
I was having a heck of a time figuring out the correct collabora subdomain proxy config for SWAG. I came across this site which helped me successfully get Nextcloud, SWAG & Collabora working. The config at that link worked for me -- I only changed line 37 to my Unraid IP. Sharing here in case it helps anyone else.
I wonder how you got this working. I added the aliasgroup1 variable like you recommended. I am on unraid 6.11.5 currently, running SWAG, nextcloud, and mariaDB setup and of course trying to use the collabora app with nextcloud now for online document editing and just having no luck. I will attach my collabora.subdomain.conf file, and screenshots of my setup.
I get a green checkmark in nextcloud, but when I load documents it fails every time. Here also is the collabora logs with errors. I have tried to follow multiple guides with no luck. I can provide any more info on my setup as needed.
I use pihole and internally, for nextcloud.* I resolve local IP of my reverse proxy. Same for collabora (office.*). In nextcloud's docker, I use extra parameter to use pihole proxy (by default, servers on my server segment don't get pihole proxy) and that allows nextcloud to resolve locally collabora's IP. Since Spaceinvader mentioned that both collabora and nextcloud need to be able to resolve each other, I tried to add the same extra parameter to collabora's docker. Otherwise, if collabora was to resolve it, it would resolve public IP.
Under this link, the Collabora editor is shown. The Collabora editor is a web based version of LibreOffice that makes it possible for students to simultaneously collaborate on a document (text, spreadsheet or presentation).
@bjo: Not sure if I'm the right person for that. My knowledge of the ins and outs of collabora is rather superficial. But I'm happy to ping you / let you know if I notice something on the tiny instance I run as I did in the past with theYinYeti
@bjo: How do you feel about removing libssl1.0.0 = openssl-1.0 from _upstream_equiv? I just checked and it seems the dependency to libssl1.0.0 has been removed from upsteam .deb-package and the collabora aur package builds just fine without it. The last upstream release of openssl 1.0.2 is now >3 years old, unmaintained and should not be considered safe anyway.
df19127ead