Using Collabora with MIAB NextCloud?

Unsupported Modifications
22

Have you registered your name servers with Zuver. I tried Skyping you but there was no answer. I’m working all day tomorrow. Feel free to call me anytime. I’ll be available between 11:00am. to 9pm. UTC-7

23

Cheers! Sorry about that, I thought I had missed you for the day and might have been asleep already. I’ll aim for about 10 am here which I think works out to be about 5 pm there.

Thanks again.

24

Hi @pupsncats, just wondering if you’re around atm? I’m on Skype.

I seem to now have DNS sorted (didn’t know about custom DNS in MiaB). Once I added an A record for my subdomain it resolved :slight_smile:

Now it’s just a matter of not connecting (i.e. MiaB not connecting to Collabora). I have created the letsencrypt files, and included the full paths in the nginx config file (I also tried apache).

Right now apache is set to listen on a random port but all the modules for reverse proxy, ssl, etc are enabled and I am using nginx as per your instructions.

I tried calling on Skype but no answer - you’re working though, so it’s possible that you’re busy.

Thank you :slight_smile:

25

I know it’s been a while, but I’m just wondering if anyone has recently set this up with a newer version of miab (v73) and a newer Collabora server (Ubuntu 24.04)?

I have set it all up and both the test urls work.

https://office.mydomain.co.za/hosting/capabilities
https://office.mydomain.co.za/hosting/discovery

Also, when I set the Office url in Nextcloud it says it’s connected to the server. I set the WOPI ip address range too.

When click a document to edit it however, it doesn’t open and just says
image

I checked /var/log/nginx/access.log and error.log, but nothing shows that’s relevant.

Is there a log somewhere else where this would be logged?

26

I found the log in /home/user-data/owncloud/nextcloud.log. Part of the last line shows:

"CustomMessage":"Failed to fetch the Collabora capabilities endpoint: Client error: GET https://box2.mymiabserver.co.za/cloud/cloud/apps/richdocumentscode/proxy.php?req=/hosting/capabilities resulted in a 404 Not Found

So, that URL clearly does not exist on box2, so how did you get it to work?

27

I have figured out the missing parts (using the official documentation)

server {
 listen       443 ssl;
 server_name  office.server.co.za;

 ssl_protocols TLSv1.1 TLSv1.2;
 ssl_certificate /etc/letsencrypt/live/office.server.co.za/fullchain.pem;
 ssl_certificate_key /etc/letsencrypt/live/office.server.co.za/privkey.pem;

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

 location ^~ /loleaflet {
 proxy_pass https://localhost:9980;
 proxy_set_header Host $http_host;
 }

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

 # Capabilities
 location ^~ /hosting/capabilities {
   proxy_pass https://localhost:9980;
   proxy_set_header Host $http_host;
 }

 # main websocket
 location ~ ^/cool/(.*)/ws$ {
   proxy_pass https://localhost: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 ~ ^/(c|l)ool {
   proxy_pass https://localhost:9980;
   proxy_set_header Upgrade $http_upgrade;
   proxy_set_header Connection “upgrade”;
   proxy_set_header Host $http_host;
 }

 # Admin Console websocket
 location ^~ /cool/adminws {
   proxy_pass https://localhost:9980;
   proxy_set_header Upgrade $http_upgrade;
   proxy_set_header Connection "Upgrade";
   proxy_set_header Host $http_host;
   proxy_read_timeout 36000s;
 }
}

server {
listen 80;
server_name office.server.co.za;

root /var/local/nginx/office;
}