Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Request: Collabora Online

Featured Replies

Hi guys.

I've follow the instructions on https://nextcloud.com/collaboraonline/ to integrate Collabora Online with Nextcloud, using LinuxServer's Nextcloud & LetsEncrpyt containers as the basis.

Had to follow https://icewind.nl/entry/collabora-online/ for NGINX instructions (configured on the LetsEncrypt container, adding "office" to the list of my subdomains).

The only things I had to change from the instructions in the links is:

  1. replacing "127.0.0.1" to my unRAID IP on the docker command line
  2. replace "localhost" to my unRAID IP on the NGINX configuration

 

Is there someone who can create an unRAID compatible template for the CODE container?

I really like it to be managed like all my other containers, but dunno where to start.

 

Thanks

  • Author

Anyone?

Or can anyone point me to a starter guide to creating container template for unraid?

look in the docker fan

11 hours ago, gshlomi said:

Anyone?

Or can anyone point me to a starter guide to creating container template for unraid?

I got this up and running, see my post here: 

 

  • Author
4 hours ago, uldise said:

I got this up and running, see my post here: 

 

Does it enables auto-updates for the container?

38 minutes ago, gshlomi said:

Does it enables auto-updates for the container?

Sorry, i don't know..

  • Author

Doesn"t it have to be based on an unRAID container template for that?

1 minute ago, gshlomi said:

Doesn"t it have to be based on an unRAID container template for that?

as far as i know, there is no template for unRAID jet.. 

1 hour ago, gshlomi said:

Doesn"t it have to be based on an unRAID container template for that?

 

No, you could have a container that never updates with an Unraid template.

5 minutes ago, CHBMB said:

 

No, you could have a container that never updates with an Unraid template.

And conversely a container that auto updates that does not have an unRaid template.

  • Author
5 hours ago, Squid said:

And conversely a container that auto updates that does not have an unRaid template.

Thanks

That's what I've been looking for...

  • 8 months later...
On 5/11/2017 at 8:30 AM, gshlomi said:

Hi guys.

I've follow the instructions on https://nextcloud.com/collaboraonline/ to integrate Collabora Online with Nextcloud, using LinuxServer's Nextcloud & LetsEncrpyt containers as the basis.

Had to follow https://icewind.nl/entry/collabora-online/ for NGINX instructions (configured on the LetsEncrypt container, adding "office" to the list of my subdomains).

The only things I had to change from the instructions in the links is:

  1. replacing "127.0.0.1" to my unRAID IP on the docker command line
  2. replace "localhost" to my unRAID IP on the NGINX configuration

 

Is there someone who can create an unRAID compatible template for the CODE container?

I really like it to be managed like all my other containers, but dunno where to start.

 

Thanks

 

Would you be able to share your collabora docker and nginx config...

 

I am following the same guides and all I am getting is "504 Gateway Time-out" within next cloud.

On the collabora side I get the following error in the log

wsd-00026-00034 18:16:45.912139 [ websrv_poll ] ERR Socket #21 SSL BIO error: closed (0).| ./net/SslSocket.hpp:255

 

Here is my docker config:

Collabora.thumb.PNG.8d5311ce8515c174473564e11a18f399.PNG

 

Nginx config:

server {

	listen 443 ssl;
	root /config/www ;
	index index.html index.htm index.php;

	server_name office.xxx.com;

	ssl_certificate /config/keys/letsencrypt/fullchain.pem;
	ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
	
	# static files
    location ^~ /loleaflet {
        proxy_pass https://192.168.32.10:9980;
        proxy_set_header Host $http_host;
    }

    # WOPI discovery URL
    location ^~ /hosting/discovery {
        proxy_pass https://192.168.32.10:9980;
        proxy_set_header Host $http_host;
    }

   # main websocket
   location ~ ^/lool/(.*)/ws$ {
       proxy_pass https://192.168.32.10:9980;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "Upgrade";
       proxy_set_header Host $http_host;
       proxy_read_timeout 36000s;
   }
   
   # download, presentation and image upload
   location ~ ^/lool {
       proxy_pass https://192.168.32.10:9980;
       proxy_set_header Host $http_host;
   }
   
   # Admin Console websocket
   location ^~ /lool/adminws {
       proxy_pass https://192.168.32.10:9980;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "Upgrade";
       proxy_set_header Host $http_host;
       proxy_read_timeout 36000s;
   }
}

 

 

  • 3 weeks later...
  • Author

Where did you install the container from?

I've used the CLI, so my container settings looks totally different.

This is the command parameters I've used:

-t -d -p 192.168.1.100:9980:9980 -e 'domain=nc\\.XXXXX\\.org' -e "username=admin" -e "password=XXXXXXXXX" --restart always --cap-add MKNOD

with the domain parameter points to my Nextcloud URL.

This are my NGINX definitions for CODE:

# Collabora Online server block
server {
    listen 443 ssl;
    server_name office.*;
	include /config/nginx/ssl.conf;

    # static files
    location ^~ /loleaflet {
        proxy_pass https://192.168.1.100:9980;
        proxy_set_header Host $http_host;
    }

    # WOPI discovery URL
    location ^~ /hosting/discovery {
        proxy_pass https://192.168.1.100:9980;
        proxy_set_header Host $http_host;
    }

    # websockets, download, presentation and image upload
    location ^~ /lool {
        proxy_pass https://192.168.1.100:9980;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $http_host;
    }
}

 

Where did you install the container from?
I've used the CLI, so my container settings looks totally different.
This is the command parameters I've used:
-t -d -p 192.168.1.100:9980:9980 -e 'domain=nc\\.XXXXX\\.org' -e "username=admin" -e "password=XXXXXXXXX" --restart always --cap-add MKNOD

with the domain parameter points to my Nextcloud URL.
This are my NGINX definitions for CODE:

# Collabora Online server blockserver {   listen 443 ssl;   server_name office.*;include /config/nginx/ssl.conf;   # static files   location ^~ /loleaflet {       proxy_pass https://192.168.1.100:9980;       proxy_set_header Host $http_host;   }   # WOPI discovery URL   location ^~ /hosting/discovery {       proxy_pass https://192.168.1.100:9980;       proxy_set_header Host $http_host;   }   # websockets, download, presentation and image upload   location ^~ /lool {       proxy_pass https://192.168.1.100:9980;       proxy_set_header Upgrade $http_upgrade;       proxy_set_header Connection "upgrade";       proxy_set_header Host $http_host;   }}

 

That's how I've got mine setup too....

Sent from my LG-H815 using Tapatalk

  • 4 weeks later...

Dear firends, I am clueless and lost on installing collabora and integrating it with nextcloud. On my 6.4.1 unRAID, here is a summary of my setup:

 

Nextcloud is working with letsencrypt reverse proxy on https://nextcloud.mydomain.com. This is installed using @CHBMB 's excellent guide.

 

I installed collabora using CLI:

docker pull collabora/code
docker run -t -d -p 192.168.1.100:9980:9980 -e 'domain=nextcloud\\.mydomain\\.com' -e "username=admin" -e "password=mypass"  --restart always --cap-add MKNOD collabora/code

Then, I created a server block file in /mnt/user/appdata/letsencrypt/nginx/site-confs/collabora alongside default and nextcloud files.

# Collabora Online server block
server {
    listen 443 ssl;
    server_name office.mydomain.com;
        include /config/nginx/ssl.conf;

    # static files
    location ^~ /loleaflet {
        proxy_pass https://192.168.1.100:9980;
        proxy_set_header Host $http_host;
    }

    # WOPI discovery URL
    location ^~ /hosting/discovery {
        proxy_pass https://192.168.1.100:9980;
        proxy_set_header Host $http_host;
    }

    # websockets, download, presentation and image upload
    location ^~ /lool {
        proxy_pass https://192.168.1.100:9980;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $http_host;
#        proxy_read_timeout 36000s;
    }

}

Restarted letsencrypt without any error. Also installed collabora plugin in nextcloud and linked it to https://office.mydomain.com.

 

Unfortunately, this setup is not working. Two symptomps:

 

1. When I try to connect https://office.mydomain.com, "Welcome to nginx!" page comes up.

2. When I try to click on a libreoffice document in nextcloud, I receive error message given below:

 

Internal Server Error
The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.

Technical details
Remote Address: 172.17.0.1
Request ID: CqAQZjtoonFPotqrhNDX

Obviously, I am doing something wrong. I would appreciate any help. Thank you.

My problem is now fixed. For the other users having problems, the conf files in my post are working. I made a stupid mistake by not entering subdomain in letsencrypt edit.

 

By the way, @CHBMB, would you be so kind and create "elastic search" container? I will post this request separately, anyway.

 

Thanks.

My problem is now fixed. For the other users having problems, the conf files in my post are working. I made a stupid mistake by not entering subdomain in letsencrypt edit.
 
By the way, [mention=6219]CHBMB[/mention], would you be so kind and create "elastic search" container? I will post this request separately, anyway.
 
Thanks.
Up until yesterday I hadn't even heard of elastic search. I need to research....

Sent from my LG-H815 using Tapatalk

  • 4 months later...

Just commenting here because I would still be very interested in an unRAID Collabora template. Can't seem to get it working with reverse proxy despite following instructions linked above.

  • 2 weeks later...

Yea, I have been struggling for months.  I can never get them integrated

On 3/10/2018 at 9:30 AM, sse450 said:

My problem is now fixed. For the other users having problems, the conf files in my post are working. I made a stupid mistake by not entering subdomain in letsencrypt edit.

 

By the way, @CHBMB, would you be so kind and create "elastic search" container? I will post this request separately, anyway.

 

Thanks.

2

Hey, thank you for the instructions. I am also trying to setup Nextcloud with a reverse proxy in conjunction with Letsencrypt, everything works, except the Collabora. Can you share your settings, please? So confused. Thanks!!!

  • 1 month later...
On 8/22/2018 at 2:39 PM, pervin_1 said:

Hey, thank you for the instructions. I am also trying to setup Nextcloud with a reverse proxy in conjunction with Letsencrypt, everything works, except the Collabora. Can you share your settings, please? So confused. Thanks!!!

+1 on this. Have you found any working guides for integrating collabora with nextcloud on unraid?

  • 2 weeks later...
On 9/26/2018 at 11:37 AM, adoucette said:

+1 on this. Have you found any working guides for integrating collabora with nextcloud on unraid?

Sorry was away for a while, I see that you replied to my comment back in Sep. If you are interested, I am willing to write a tutorial with instructions and commands get it to work. PM me please and I will post the instructions here, it's kinda long 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.