Hey there,
I’ve got a weird issue with my Seafile Server & OnlyOffice. Whenever I load a document I only get a blank white screen (with the Seafile bar up top) in Safari. Any other browser works fine, it’s JUST Safari. I cannot resolve the issue by reloading the page. What works is to reset the User-Agent in the Developer Tools, when ever I do that, the document loads immediately. Once I reload the page, it’s gone again. To clarify: I don’t need to switch User-Agents, it’s sufficient to just reload the “standard” option by clicking on it. Anyone had anything similar? Any idea what the issue could be?
My setup:
Unraid 6.12.15
Seafile CE 13.0.22 Docker Container
OnlyOffice Document Server 9.4.0.129 Docker Container
It’s not exclusively a problem of this combination of versions. I’ve had the problem with OnlyOffice version 8 and Seafile 12, as well…
EDIT: It’s ONLY when OnlyOffice is supposed to load files. .md/.txt/.html etc. which load the Seafile Editor work just fine.
Greetings,
Thiemo
I have indeed narrowed it down now. It seems to be the document_editor_service_worker.js which is stored in the cache and returns a 404 error in the console. A hard reload will immediately fix the issue, but once the file is cached just once, it’ll stop working again. I have tested this with the current EuroOffice built, which is a OnlyOffice fork and the issue is identical. I’ve tried implementing a Response Header Transform Rule through Cloudflare, which aims to prevent caching. But the problem persists. I don’t really know why that is though. But it has to be something to do with caching, right?
EDIT: It is not the service worker. I’ve blocked the script manually via a WAF rule in cloudflare. I confirmed it’s not being loaded, but the issue persists.
EDIT: Could be the “seafile-editor.json”. It returns an error.
EDIT: This is indeed a bug. The expected path was /media/seafile-editor/locales/de-DE/seafile-editor.json, but it is actually located here: media/seafile-editor/locales/de/seafile-editor.json. Fixing this manually resolves the error, but the initial problem persists. This was not the issue.
Additional findings in the network tab
Blank Page: (document doesn’t load)
media/js/base.js?t=1536127546642
web-apps/apps/api/documents/api.js (on the Document Server)
– STOP –
After Hard Reset: (document loads)
media/js/base.js?t=1536127546642
/media/assets/scripts/i18n/de/djangojs.js?v=13.0.24
/media/assets/frontend/static/js/runtime.8cf6253b.bd1257c45e88.js
/media/assets/frontend/static/js/commons.b6bcae5d.63e9153791a3.js
/media/assets/frontend/static/js/viewFileOnlyoffice.d30601f0.e45973bf8c6c.js
/media/assets/scripts/lib/jquery.min.c9771cc3e90e.js
etc.
I’ve tested some more browsers and machines:
- Safari doesn’t work
- Brave on Mac works
- Brave on Windows doesn’t work
- Firefox doesn’t work on my Windows machine
- Firefox works on my brothers Windows machine
Clearing the cache and deleting all website data doesn’t solve the issue. How can that be?
EDIT:
Comparing the missing deployment of files every single time the document is not being opened the code within the “filename.docx” doesn’t deploy this script /media/assets/scripts/i18n/de/djangojs.js?v=13.0.24. The last network activity is the api.js file initiated by the js-Block that ends at the line before.