Document Server Update in Seafile Fails

Questions/problems on Docker
Post Reply
Posts: 55
Joined: Tue Jun 09, 2015 2:29 am

Document Server Update in Seafile Fails

Post by Merc » Mon Apr 02, 2018 9:13 pm

I just attempted to update the Docker image for the OnlyOffice Document Server running in Subdirectory (Subfolder) mode on Seafile 6.2.5 CE without success. When I open a document using the co-located document server based on the latest/current image I get a white page.

In Chromium the Javascript error on the resultant document page is:

"Failed to load resource: the server responded with a status of 502 (Bad Gateway) api.js"
"Uncaught ReferenceError: DocsAPI is not defined"

At the time of this post the latest version (or tag) of onlyoffice/documentserver is, released five days ago. The previous version of the Document Server is released three months ago.

If I roll back to the previous image ( things work again.

The procedure used is:

Stop Seafile
Stop oods (the name of onlyoffice/documentserver)
Delete container oods
Update (pull) latest onlyoffice/documentserver
Spin-up new container using latest onlyoffice/documentserver using:

sudo docker run -dit -p 88:80 --restart always --name oods onlyoffice/documentserver

Start Seafile
Restart Nginx

No changes were made to the server or its configuration. Memcached is not employed by Seafile.

The operative string in Seafile that points to oods is:

ONLYOFFICE_APIJS_URL = 'http(s)://{Server_IP or FQDN}/onlyofficeds/web-apps/apps/api/documents/api.js'

Is this string still valid for document server

Thanks for your comments & assistance. I appreciate your help.

Seafile CE 6.2.5
Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)

Posts: 1817
Joined: Tue Oct 11, 2016 2:34 pm

Re: Document Server Update in Seafile Fails

Post by Maxim » Tue Apr 03, 2018 8:03 am

Hello Merc!
Access to the API was not changed in 5.1 version

Code: Select all


Post Reply