Request: Collabora Online


Recommended Posts

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

Link to comment
  • 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;
   }
}

 

 

Link to comment
  • 3 weeks later...

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;
    }
}

 

Link to comment
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

Link to comment
  • 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.

Link to comment

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.

Link to comment
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

Link to comment
  • 4 months later...
  • 2 weeks later...
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!!!

Link to comment
  • 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?

Link to comment
  • 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 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.