Updated Collabora, now unable to open documents

dom134 · October 14, 2016, 8:23pm

I did have a working Collabora office app working, but recently updated. Now I am unable to open any documents. The post-update error message states:

Well, this is embarrassing, we cannot connect to your document. Please try again.

My docker log [urls and ips changed] states:

wsd-00024-05 00:06:02.225755 [ client_req_hdl ] Request from 172.17.0.1:47716: POST /loleaflet/1.8.4/loleaflet.html?WOPISrc=https%3A%2F%2Fwww.dom134.com%2Fnextcloud%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F203620&title=php.odt&lang=en&closebutton=1&revisionhistory=1 HTTP/1.1 / Host: office.dom134.com / User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 / Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 / Accept-Language: en-US,en;q=0.5 / Accept-Encoding: gzip, deflate, br / DNT: 1 / Upgrade-Insecure-Requests: 1 / Content-Type: application/x-www-form-urlencoded / X-Forwarded-For: 88.88.888.888 / X-Forwarded-Host: office.dom134.com / X-Forwarded-Server: office.dom134.com / Connection: Keep-Alive / Content-Length: 45
wsd-00024-05 00:06:02.226076 [ client_req_hdl ] Preprocessing file: /usr/share/loolwsd//loleaflet/dist/loleaflet.html
wsd-00024-02 00:06:03.634363 [ client_req_hdl ] Request from 172.17.0.1:47720: GET /lool/https%253A%252F%252Fwww.dom134.com%252Fnextcloud%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F203620%3Faccess_token=qeUnp2EEXI6F0IlJLBU7cwiSmV8PiLwd/ws HTTP/1.1 / Host: office.dom134.com / User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 / Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 / Accept-Language: en-US,en;q=0.5 / Accept-Encoding: gzip, deflate, br / Sec-WebSocket-Version: 13 / origin: https://office.dom134.com / Sec-WebSocket-Extensions: permessage-deflate / Sec-WebSocket-Key: 5JfxEr5wtG4iVaUk/ToVJQ== / DNT: 1 / Pragma: no-cache / Cache-Control: no-cache / X-Forwarded-For: 88.88.888.888 / X-Forwarded-Host: office.dom134.com / X-Forwarded-Server: office.dom134.com / Connection: Keep-Alive
wsd-00024-02 00:06:03.634495 [ client_req_hdl ] Handling GET: /lool/https%253A%252F%252Fwww.dom134.com%252Fnextcloud%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F203620%3Faccess_token=qeUnp2EEXI6F0IlJLBU7cwiSmV8PiLwd/ws
wsd-00024-02 00:06:03.634559 [ client_ws_0004 ] Thread started.
wsd-00024-02 00:06:03.634606 [ client_ws_0004 ] Post request: [/lool/https%253A%252F%252Fwww.dom134.com%252Fnextcloud%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F203620%3Faccess_token=qeUnp2EEXI6F0IlJLBU7cwiSmV8PiLwd/ws]
wsd-00024-02 00:06:03.634723 [ client_ws_0004 ] ClientRequestHandler::handleRequest: BadRequestException: Invalid or unknown request.
wsd-00024-02 00:06:03.634801 [ client_ws_0004 ] Thread finished.

Does anyone have any ideas?

Poach · October 14, 2016, 8:54pm

I’m having the exact same issue, but I just installed Collabora yesterday and haven’t been able to get it working. I think it may have something to do with the URL it’s passing. The url looks like it’s been double encoded…

/lool/https%253A%252F%252Fcloud.DOMAIN.org%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F484%3Faccess_token%3DlcZ5cQcNT6unGjvXOn5PlzQOLIImhVVl/ws
VS
/lool/https%3A%2F%2Fcloud.DOMAIN.org%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F484?access_token=lcZ5cQcNT6unGjvXOn5PlzQOLIImhVVl/ws

I’m running Ubuntu 16.04LTS (Upgraded from 14.14), Apache Apache/2.4.18 (Ubuntu), PHP 7.0.8-0ubuntu0.16.04.3, using chrome to access.

Here are my Docker logs for Collabora

> wsd-00022-03 00:44:12.962918 [ client_req_hdl ] Request from 172.17.0.1:39952: GET /hosting/discovery HTTP/1.1 / Host: office.DOMAIN.org / User-Agent: ownCloud Server Crawler / X-Forwarded-For: IP.IP.IP / X-Forwarded-Host: office.DOMAIN.org / X-Forwarded-Server: office.DOMAIN.org / Connection: Keep-Alive
> wsd-00022-03 00:44:12.963012 [ client_req_hdl ] Handling GET: /hosting/discovery
> wsd-00022-03 00:44:12.963043 [ client_ws_0021 ] Thread started.
> wsd-00022-03 00:44:12.966873 [ client_ws_0021 ] Sent discovery.xml successfully.
> wsd-00022-03 00:44:12.967045 [ client_ws_0021 ] Thread finished.
> wsd-00022-05 00:44:14.093350 [ client_req_hdl ] Request from 172.17.0.1:39958: POST /loleaflet/1.8.4/loleaflet.html?WOPISrc=https%3A%2F%2Fcloud.DOMAIN.org%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F484&title=ByLaws%202011-05-08.docx&lang=en&closebutton=1&revisionhistory=1 HTTP/1.1 / Host: office.DOMAIN.org / Cache-Control: max-age=0 / Origin: null / Upgrade-Insecure-Requests: 1 / User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.50 Safari/537.36 / Content-Type: application/x-www-form-urlencoded / Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 / Accept-Encoding: gzip, deflate, br / Accept-Language: en-US,en;q=0.8 / X-Forwarded-For: IP.IP.IP.IP / X-Forwarded-Host: office.DOMAIN.org / X-Forwarded-Server: office.DOMAIN.org / Connection: Keep-Alive / Content-Length: 45
> wsd-00022-05 00:44:14.093541 [ client_req_hdl ] Preprocessing file: /usr/share/loolwsd//loleaflet/dist/loleaflet.html
> wsd-00022-06 00:44:14.409108 [ client_req_hdl ] Request from 172.17.0.1:39964: GET /lool/https%253A%252F%252Fcloud.DOMAIN.org%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F484%3Faccess_token%3DlcZ5cQcNT6unGjvXOn5PlzQOLIImhVVl/ws HTTP/1.1 / Host: office.DOMAIN.org / Pragma: no-cache / Cache-Control: no-cache / Origin: https://office.DOMAIN.org / Sec-WebSocket-Version: 13 / User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.50 Safari/537.36 / Accept-Encoding: gzip, deflate, sdch, br / Accept-Language: en-US,en;q=0.8 / Sec-WebSocket-Key: uhEb0vN93snCKRa/0F9tkA== / Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits / X-Forwarded-For: IP.IP.IP.IP / X-Forwarded-Host: office.DOMAIN.org / X-Forwarded-Server: office.DOMAIN.org / Connection: Keep-Alive
> wsd-00022-06 00:44:14.409201 [ client_req_hdl ] Handling GET: /lool/https%253A%252F%252Fcloud.DOMAIN.org%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F484%3Faccess_token%3DlcZ5cQcNT6unGjvXOn5PlzQOLIImhVVl/ws
> wsd-00022-06 00:44:14.409234 [ client_ws_0022 ] Thread started.
> wsd-00022-06 00:44:14.409257 [ client_ws_0022 ] Post request: [/lool/https%253A%252F%252Fcloud.DOMAIN.org%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F484%3Faccess_token%3DlcZ5cQcNT6unGjvXOn5PlzQOLIImhVVl/ws]
> wsd-00022-06 00:44:14.409324 [ client_ws_0022 ] ClientRequestHandler::handleRequest: BadRequestException: Invalid or unknown request.
> wsd-00022-06 00:44:14.409368 [ client_ws_0022 ] Thread finished.

timar · October 14, 2016, 10:39pm

Are you using the latest version of Collabora Online Connector (richdocuments)?

Poach · October 15, 2016, 1:49am

It’s at 1.1.7, and I just installed it for the first time earlier this week

dom134 · October 15, 2016, 3:42am

Hello Timar

I pulled the latest collabora/code 2 days ago; on my app list I also have:

richdocuments: 1.1.7

Interestingly when I pull in the latest code I get:

docker pull collabora/code
Using default tag: latest
latest: Pulling from collabora/code

bf5d38688883: Already exists
a3ed95caeb02: Already exists

Should there be 2 ids there?
When I investigate docker ps, though, I only have the one container_id

Thanks

dev0 · October 15, 2016, 7:32am

@dom134 use: docker ps -a
perhaps you have a stopped instance.
that one you can remove with docker rm

guddl · October 15, 2016, 9:36am

Hi,

had a working Collabora Office … then I updated the container and get exactly the same error.

Nextcloud 10.0.1
Collabora Online 1.1.7

Cheers,
Andreas

dev0 · October 15, 2016, 9:57am

I still have the old version, I extracted it with docker export <container_ID> > file.tar.gz
altough perhaps there are changes paths to the jquery files, so you might have them too and alter the path to them.
If you want try to import that, perhaps I can transfer it to anyone of you.
Its about 350 MB in size

dom134 · October 15, 2016, 2:57pm

Hello I tried docker ps -a and this is what I got

docker ps -a
CONTAINER ID IMAGE 5bcf193d1124 collabora/code 326fb2410d11 collabora/code 0e12b90ca878 collabora/code 8e82ee6fcdda collabora/code c038a2ca9dd2 36f9a73c326b 552419a21268 36f9a73c326b 5fb025c83fc3 36f9a73c326b beb415607568 36f9a73c326b 8bdb73bea437 36f9a73c326b 700ce2eaa654 36f9a73c326b c7e6396971e2 36f9a73c326b 9a1bfc35165f 36f9a73c326b 24ccc14b35ba 36f9a73c326b 38cb1250e27a 36f9a73c326b cc11d70938dc 36f9a73c326b 52f3c764a7a2 36f9a73c326b 445419e4b1d8 e2c7544e3e42 3b1d3b46285e e2c7544e3e42 b0ab157e3926 e2c7544e3e42 93a95609de58 e2c7544e3e42 1fecf099786d e2c7544e3e42 COMMAND CREATED STATUS PORTS NAMES
“/bin/sh -c 'bash sta” 17 hours ago Up 17 hours 127.0.0.1:9980->9980/tcp elegant_bhabha
“/bin/sh -c 'bash sta” 41 hours ago Exited (137) 18 hours ago sleepy_jennings
“/bin/sh -c 'bash sta” 43 hours ago Exited (128) 42 hours ago gloomy_meninsky
“/bin/sh -c 'bash sta” 43 hours ago Exited (128) 43 hours ago tiny_hoover
“/bin/sh -c 'bash sta” 2 weeks ago Exited (128) 2 days ago distracted_sammet
“/bin/sh -c 'bash sta” 3 weeks ago Exited (128) 3 weeks ago reverent_feynman
“/bin/sh -c 'bash sta” 4 weeks ago Exited (128) 3 weeks ago prickly_banach
“/bin/sh -c 'bash sta” 4 weeks ago Created furious_hugle
“/bin/sh -c 'bash sta” 4 weeks ago Exited (128) 4 weeks ago furious_swanson
“/bin/sh -c 'bash sta” 4 weeks ago Exited (128) 3 weeks ago boring_wing
“/bin/sh -c 'bash sta” 5 weeks ago Exited (128) 8 days ago romantic_wozniak
“/bin/sh -c 'bash sta” 5 weeks ago Exited (128) 3 days ago agitated_roentgen
“/bin/sh -c 'bash sta” 5 weeks ago Exited (128) 5 weeks ago hopeful_snyder
“/bin/sh -c 'bash sta” 5 weeks ago Exited (128) 5 weeks ago determined_morse
“/bin/sh -c 'bash sta” 5 weeks ago Exited (128) 2 weeks ago determined_ardinghelli
“/bin/sh -c 'bash sta” 5 weeks ago Exited (128) 2 days ago cranky_jang
“/bin/sh -c 'bash sta” 10 weeks ago Exited (128) 5 weeks ago sad_sammet
“/bin/sh -c 'bash sta” 10 weeks ago Exited (128) 4 weeks ago cranky_stallman
“/bin/sh -c 'bash sta” 10 weeks ago Exited (128) 4 weeks ago prickly_albattani
“/bin/sh -c 'bash sta” 11 weeks ago Exited (128) 2 weeks ago romantic_lumiere
“/bin/sh -c 'bash sta” 12 weeks ago Exited (0) 11 weeks ago 127.0.0.1:9980->9980/tcp pensive_goldstine

I did a

docker rm

on all the container_ids, but to no avail. I then tried

docker images

and this is what I had:

docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
collabora/code latest 73e1b4b59383 3 days ago 1.131 GB
collabora/code 36f9a73c326b 6 weeks ago 1.131 GB
e2c7544e3e42 12 weeks ago 1.003 GB

I did a

docker rmi

on all the image_ids, but again I still get the ‘embarrasing’ caption.

dev0 · October 15, 2016, 3:27pm

uhm, what did you do with your docker? you have a mess as hell, are you using anything else then collabora?
But I don’t think that collabora is not working is your fault, I assume that the last update of collabora made it somehow incompatible with nextcloud.

You did in your case remove your containers and delete your images, so it redownloads it again.

Unfortunately collabora only releases the latest tag and not older versions of it, so there seems to be a short term solution and/or a ling term one.

Longterm: the guys at nextcloud or collabora are fixing that again.
Shortterm: I can send you my saved container after I patched the jquerystuff in and you have to import it.

Or anyone else has a clean, old collabora/code image he can save it out, and share.

dom134 · October 15, 2016, 3:35pm

I think the ‘mess’ was just because I was only stopping my containers and not removing them. I am not running Documents or anything else that causes issues. After a tidy-up I now have:

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
454688ad86e4 collabora/code “/bin/sh -c 'bash sta” 39 minutes ago Up 39 minutes 127.0.0.1:9980->9980/tcp ecstatic_lumiere

and my images are just:

docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
collabora/code latest 73e1b4b59383 3 days ago 1.131 GB

I don’t know, I just feel as though there is something in this last image that is causing an upset on my particular system. Maybe I should have kept a previous image!

Thanks for your offer dev0; however I think I will wait until the next image gets released.

dev0 · October 15, 2016, 3:37pm

that can take a while:

dom134 · October 15, 2016, 3:40pm

Looking at the timescales, I might get it in time for Christmas - Ho Ho Ho!

dev0 · October 15, 2016, 3:48pm

perhaps filing an issue with logs at this location may help too:

timar · October 15, 2016, 8:25pm

Are you using the reverse proxy, that is recommended on Nextcloud’s page? Please note that URL scheme has changed, because it was not useable with HAProxy.

You need:
# Main websocket
ProxyPassMatch “/lool/(.*)/ws$” wss://127.0.0.1:9980/lool/$1/ws
Instead of:

Main websocket

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

I hope this helps.

Christian_H · October 15, 2016, 8:48pm

I did a fresh installation of Collabora today. Ran into this issue.

Your suggestions fixed it for me. I guess the tutorial needs an update.

dom134 · October 15, 2016, 9:01pm

What a star, Timar! It works again!

guddl · October 16, 2016, 9:27am

@jospoortvliet Can someone “adjust” the documentation Collabora Online in Nextcloud

Thanks.
Andreas

dev0 · October 16, 2016, 10:11am

I tried it out too, that works perfect.
@guddl about the documentationupdate: I am looking for that guy too, somehow they are well hidden.

guddl · October 16, 2016, 10:29am

If I remember right - Jos wrote the dokumentation