Can't connect to Collabora Online :/


#1

Collabora Online: Cannot connect to the host “http://office.sptmin.com:9980”.
Please ask your administrator to check the Collabora Online server setting. The exact error message was: cURL error 7: Failed to connect to office.sptmin.com port 9980: Connection refused

This is the error I’m getting^

I’m not sure what I did wrong, since I followed the instructions exactly as given. I’m using Digital Ocean and the servers run apache.


#2

If you followed the instructions and setup Apache as proxy, you should skip entering the port number in NextCloud.


#3

Well now I’m having a new problem - the apply button won’t work :confounded:


#4

I’ve the same problem. apply button doesn’t work.


#5

The “Apply” button seems to be very slow and doesn’t give feedback, but it seems that clicking and waiting some time does indeed work. Personally, I also had to use Firefox, since Safari didn’t work.

Here is another solution:


#6

I got it (the apply button) to work by disabling the documents app. However, the collabra online app still won’t work. After removing :9980 from the URL (as I am using the reverse proxy as recommended), I get a new error:

Collabora Online unknown error: Client error response [url] https://office.sptmin.com/hosting/discovery [status code] 404 [reason phrase] Not Found


#7

https://office.sptmin.com/hosting/discovery is not accessible and delivers a 404, it should deliver something like https://office.cloud.wtf/hosting/discovery

So there is pretty certainly a configuration issue in your reverse proxy :wink: – Posting and comparing your configuration with the required one might help.


#8

Sorry for the delay. I have some pressing things to do but I will try to get around to this soon.


#9

<VirtualHost *:443>
ServerName office.sptmin.com:443

SSL configuration, you may want to take the easy route instead and use Lets Encrypt!

SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/office.sptmin.com/cert.pem
SSLCertificateChainFile /etc/letsencrypt/live/office.sptmin.com/chain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/office.sptmin.com/privkey.pem
SSLProtocol all -SSLv2 -SSLv3
SSLCipherSuite ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS
SSLHonorCipherOrder on

Encoded slashes need to be allowed

AllowEncodedSlashes On

Container uses a unique non-signed certificate

SSLProxyEngine On
SSLProxyVerify None
SSLProxyCheckPeerCN Off
SSLProxyCheckPeerName Off

keep the host

ProxyPreserveHost On

static html, js, images, etc. served from loolwsd

loleaflet is the client part of LibreOffice Online

ProxyPass /loleaflet https://127.0.0.1:9980/loleaflet retry=0
ProxyPassReverse /loleaflet https://127.0.0.1:9980/loleaflet

WOPI discovery URL

ProxyPass /hosting/discovery https://127.0.0.1:9980/hosting/discovery retry=0
ProxyPassReverse /hosting/discovery https://127.0.0.1:9980/hosting/discovery

Main websocket

ProxyPass /lool/ws wss://127.0.0.1/lool/ws

Admin Console websocket

ProxyPass /lool/adminws wss://127.0.0.1:9980/lool/adminws

Download as, Fullscreen presentation and Image upload operations

ProxyPass /lool https://127.0.0.1/lool
ProxyPassReverse /lool https://127.0.0.1/lool

This is what I’ve got. I’m stumped as to where I went wrong.


#10

Any idea what could be wrong? I’m thinking of trying it again from scratch.

UPDATE: Resinstalled from scratch, took great pains to follow everything correctly… still getting a 404 error no matter what port I use or don’t use.

I’m stumped and frustrated :frowning:


#11

I have exactly the same error, everything appears correct. If I got to https://office.mydomain.com/hosting/discovery I see the XML with a valid SSL certificate. Yet Like you I get the below error when trying to access from within NextCloud.

Collabora Online unknown error: Client error response [url] https://office.mydomain.com/hosting/discovery [status code] 404 [reason phrase] Not Found
Please contact the “https://office.mydomain.com:443” administrator.

Have you managed to get any further, I’ve tried all sorts for the last week and got nowhere. Do you think it points to the connector app, I tried completely uninstalling the Collabora NextCloud/OwnCloud app and checking the app folder was gone think it was called RichText or something similar then reinstalled but still made no difference.

Hoping you have got further than me or someone else can help us?


Installation Collabora & XMPP Chat
#12

Just to add to this, in the NextCloud Log it shows the following whenever I try to access Collabora:

Debug no app in context getDiscovery(): Getting discovery.xml from the cache.

Does this not point to the app not Collabora


#13

i m getting the same issue i have used digitalocean and web installer


#14

I remember something about the need to disable the “files_move” app. Can’t remember for which app, but this freed my “apply” button.


#15

Hi

i have install web installer in my domian 2.domian.com ,and its woring fine and i have added from apps Collabora Online and when i try to click open any doc i get this massage

Collabora Online: Cannot connect to the host “https://localhost:9980”.
Please ask your administrator to check the Collabora Online server setting. The exact error message was: cURL error 7: Failed to connect to localhost port 9980: Connection refused


#16

I have read on Github at collabora that nextcloud user only set https://office.domain.tld in the required field from nextcloud admin backend. Not the port! (additional settings) Since I do this collabora works but can’t read, or open documents.



#17

I had the issue too with the october collabora-image and self signed certs. Did you upgrade to the november-image? That solved it in my case.


#18

i need help i need step by step setting to install nextcloud in linex ( i know to use web installer in cpanel )
and how to setuo Collabora online in it from basic


#19

okay,

download docker
and download collabora and set it up.
look at the nextcloud howto.

then this:

the Ubuntu 16.04 LTS with the Kernel 4.4.0.21 doesn’t support the CONFIG_AUFS_XATTR=y flag I. you need a Kernel from Xenial-proposed (Ubuntu 16.04)you can use Ubuntu 14.04 but you must change the distro name in the following tutorial.

enable Testing repository:
https://wiki.ubuntu.com/Testing/EnableProposed

Edit the /etc/sources.list and add this.

deb http://archive.ubuntu.com/ubuntu/[distroname] -proposed restricted main multiverse universe

and create this file:
/etc/apt/preferences.d/proposed-updates

with following content.

Package: *
Pin: release a=[distroname]-proposed
Pin-Priority: 400

make an update and ugrade

sudo apt-get update 

sudo apt-get upgrade 

when download and installation is finished test the kernel Version with

uname -r

it must be:

4.4.0-45-generic

this Kernel has CONFIG_AUFS_XATTR=y support.

test it with:

grep AUFS_X /boot/config-4.4.0.45-generic

(it’s an Ubuntu Bug)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557776

install collabora:

docker pull collabora/code docker run -t -d -p 127.0.0.1:9980:9980 -e 'domain=cloud\\.nextcloud\\.com' --restart always --cap-add MKNOD collabora/code

also install the collabora Nextcloud app
and add only this under settings >> additional settings for collabora:

https://127.0.01 oder https://office.domain.tld

hope it works but without warranty!


#20

other people switched to devicemapper, that worked too.