OnlyOffice 7.2.0.204 produces a white page when opening a Word or Excel document. There are no errors reported on screen or in the OnlyOffice log.
Tested with Firefox 105.0, Brave Version 1.43.93 Chromium: 105.0.5195.127 (Official Build) (x86_64) and Safari Version 15.6.1 (15613.3.9.1.16, 15613). Cleared cache and restarted browser in advance.
Reverted to previous version 7.1.1.23 and all is well.
Anybody have any ideas on this?
Ubuntu 20.04.5 LTS | CE Server Version: 9.0.8 | Nginx
ADDENDUM: The standalone OnlyOffice Editor Version 7.2 (534) x86_64 similarly fails to open documents from the server. The screen flashes and a new tab is opened in the default web browser on the Seafile server login.
OnlyOffice integration stopped working for me, too. Seafile 9.0.9 and the latest OnlyOffice documentserver produce an error message âDownload failedâ. There is no error in onlyoffice.log - only info messages.
How can I revert to that version? I install and start the document server with âsudo docker run -dit -p 88:80 --restart always --name oods onlyoffice/documentserverâ.
Failed to load resource: the server responded with a status of 502 ()
seafile-tutorial.doc:55 Uncaught ReferenceError: DocsAPI is not defined
at seafile-tutorial.doc:55:21
(anonymous) @ seafile-tutorial.doc:55
Follow the white rabbit and put it in the seahub config file like explain
manual.seafile[dot]com/deploy/only_office/#configure-onlyoffice-to-use-jwt-secret
Thatâs good news @EAf6WAor . Can you say something about your installation? Which server, platform, type of OnlyOffice installation, that sort of thing? -Thanks
Running under a ESXi docker host VM with arch 5.19.6-arch1-1
Onlyoffice docker: âonlyoffice/documentserver-eeâ
Seattle docker: âdocker.seafile.top/seafileltd/seafile-pro-mc:latestâ
reverse proxy: Traefik-ee 8.2
My docker containers are setup with macvlans rather than network bridges. Traefik-ee routes traffic to containers bypassing the seafile internal nginx config.
From what i recall when installing these programs, when Iâve seen white pages in the past its been related to inter container access, or security issues like JWT tokens.
It sounds llike youâre saying there are issues on both sides. Can you say more about the problem in case @daniel.pan and/or @Vlad stop by and take a look? Do you have any documentary evidence that might help them sort out the problem? -Thanks
Very interesting setup but certainly not typical. In any case it shows that Seafile 9.X and OnlyOffice 7.2 do work together but maybe not as advertised in the Manual.
So do we need to revise the âstandardâ setup for OnlyOffice and Seafile or is there a fundamental structural flaw that needs fixing by the developers?
This should be of interest to all users. From the OnlyOffice Document Editor Blog:
JWT enabled by default
Starting from version 7.2, JWT that protects documents from unauthorized access is enabled by default. A random secret is automatically generated and just needs to be added on the side of the host application. You can obtain the default JWT secret and replace it with a custom key if required. Learn more about JWT
A discussion of how to enable JWT in Seafile is provided here in the Manual.
a) Only in the local net docs are shown. From www (LAN behind NAT) you earn a blank page.
b) http://seafile:8000/d/0fc0cf41ba1b40cfa4f1/ deliver as expected
c) http://extern.mydomain.de:8000/d/0fc0cf41ba1b40cfa4f1/ delivers white screen both internal and external
d) No difference between fowarded or blocked port 80 to onlyoffice.
e) SOLVED see below: Docs uploaded to seafile are generally not editable. Docs created within seafile are editable.
Well, you have your share of white pages too. My biggest question right now is whether anyone can expect to have a working OnlyOffice (OO) integration by following the current procedure in the Manual?
How about the desktop OO application? Any luck running that under OO 7.2.0.204 with Seafile 9.0.9?