Collabora online unable to connect to docuemnts


On a new installation (singel machine with docker container for CODA) I’m getting errors I haven’t seen befor.

The nexcloud web interface gives a popup:

And looking at the console message i have the error message:

VM2098:35 WebSocket connection to 'wss://…0%3Faccess_token%3DmpWdjYzwZD84KzFZEbTFjGLYS5U26S0n%26permission%3Dedit/ws' failed: One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 1
WrappedWebSocket @ VM2098:35
WrappedWebSocket @ VM2117:35
initialize @ bundle.js:4
e @ bundle.js:4
o.socket @ bundle.js:4
initialize @ bundle.js:5
e @ bundle.js:4 @ bundle.js:5
(anonymous) @ bundle.js:23
5../dist/errormessages @ bundle.js:24
s @ bundle.js:1
e @ bundle.js:1
(anonymous) @ bundle.js:1

Further investigation from the apache log gives: Like this one

GET /lool/ HTTP/1.1" 502 885 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36"

Internal server error (502 - Bad Gateway). My first though was that I did some configuration error in the apache reverse proxy, but the Proxy settings seems correct to me:

ProxyPassMatch "/lool/(.*)/ws$" wss://$1/ws

The access to the admin webui for CODA is available and is working fine.

If I look at the docker logs I see the a message I’ve never seen before:

wsd-00024-0029 0:02:43.254367 [ client_ws_0005 ] ERR  Error in client request handler: Connection refused| LOOLWSD.cpp:966

This error is what breaks my brain.

But the Error in the client request handler in combination with the failed: One or more reserved bits are on.

Makes me think that TCP header are messed up some how, but this is just an unconfirmed thought :slight_smile:

Has anyone seen this before and could point me in the right direction?


Replying on my own topic

This issue is fixed for me now. The simple truth was that I started the docker image with an “invisible” character in the domain name…

Collabora work fine with documents from UsersFolfer on Nextcloud server.
But I have same problem (as TS) only with documents in SMB shares.

How to solve a problem?