Collabora Integration Issue

mcit · April 18, 2017, 5:50am

Hello

I am relatively new to owncloud, I am working on a portal for our small office that uses collabora for document and spreadsheet editing. I have almost everything working, but I have one last issue to solve.

Setup is as follows:

owncloud 9.1.4 on Ubuntu server 16.04 x64
LDAP auth module up and running auth against AD on Windows Server 2008
External storage module up and running. All data stored on CIFS/SMB on Windows Server 2008

When users log in, they are presented with the correct folder structure [based on their AD group]. They have access to create, edit, delete files etc. This is working.

If I create a document with collabora in the Documents area which is stored on the Owncloud server, all works perfectly. I can edit, save, etc without issue.

However, I cannot do the same when interacting with the CIFS storage. I get the message “Well, this is embarrassing, we cannot connect to your document”

So the basic issue is that I cannot edit or even open documents that are stored in the CIFS [external storage] area.
Can anyone assist with what I can do to solve this?

My [cleansed] docker log shows the following:

anon81984126 · April 18, 2017, 5:55am

Looks like a known issue in that 3rdparty app:

github.com/owncloud/richdocuments

Unable to open files stored in an external storage

opened 09:34AM - 08 Jul 16 UTC

Kushul-ain

bug

I'm currently messing around with the CODE vm and manage to recreate this error …with every instance a created. on the owncloud of the vm itself on another server running ubuntu server 14.4 and owncloud 9.0.2 everything works fine as long as you work on the data folder of owncloud, but when you try to open a file located somewhere else on the server (that is the external storage type I use : local) Collabora Online lauch itself, try to load the file for a few seconds then give the message : 'We are sorry, this is an unexpected connection error. Please try again.' and the log look like : Exception: {"Exception":"Exception","Message":"Invalid file path.","Code":0,"Trace":"#0 \/srv\/www\/htdocs\/owncloud\/apps\/richdocuments\/controller\/documentcontroller.php(391): OCA\Richdocuments\Db\Wopi->getPathForToken('38', '0', 'Kxh6BNdidV8xTKY...')\n#1 [internal function]: OCA\Richdocuments\Controller\DocumentController->wopiCheckFileInfo('38')\n#2 \/srv\/www\/htdocs\/owncloud\/lib\/private\/appframework\/http\/dispatcher.php(159): call_user_func_array(Array, Array)\n#3 \/srv\/www\/htdocs\/owncloud\/lib\/private\/appframework\/http\/dispatcher.php(89): OC\AppFramework\Http\Dispatcher->executeController(Object(OCA\Richdocuments\Controller\DocumentController), 'wopiCheckFileIn...')\n#4 \/srv\/www\/htdocs\/owncloud\/lib\/private\/appframework\/app.php(108): OC\AppFramework\Http\Dispatcher->dispatch(Object(OCA\Richdocuments\Controller\DocumentController), 'wopiCheckFileIn...')\n#5 \/srv\/www\/htdocs\/owncloud\/lib\/private\/appframework\/routing\/routeactionhandler.php(45): OC\AppFramework\App::main('DocumentControl...', 'wopiCheckFileIn...', Object(OC\AppFramework\DependencyInjection\DIContainer), Array)\n#6 [internal function]: OC\AppFramework\routing\RouteActionHandler->__invoke(Array)\n#7 \/srv\/www\/htdocs\/owncloud\/lib\/private\/route\/router.php(291): call_user_func(Object(OC\AppFramework\routing\RouteActionHandler), Array)\n#8 \/srv\/www\/htdocs\/owncloud\/lib\/base.php(853): OC\Route\Router->match('\/apps\/richdocum...')\n#9 \/srv\/www\/htdocs\/owncloud\/index.php(39): OC::handleRequest()\n#10 {main}","File":"\/srv\/www\/htdocs\/owncloud\/apps\/richdocuments\/lib\/db\/wopi.php","Line":128}

mcit · April 18, 2017, 6:04am

Thanks for the reply. I think I skipped over that article as the error logs were not exactly matching mine.

There seems to be no fix based on that post. Does that mean everyone successfully using this document app are using it on locally stored content?

Matthew

anon81984126 · April 18, 2017, 6:28am

[quote=“mcit, post:3, topic:7069”]I think I skipped over that article as the error logs were not exactly matching mine.
[/quote]

If the message is different it might be also a similar but different bug so you could also consider to report a new bugreport over there.

I had it running for a while with locally stored content without any issue.