Blank Page in Safari and saving/reloading issues with ONLYOFFICE Doc Server & Seafile CE

Docs
1

Hey there,

I’m using OnlyOffice in this configuration:
Unraid 6.12.15
Seafile CE 13.0.22 Docker Container
OnlyOffice Document Server 9.4.0.129 Docker Container

Generally everything works fine. Documents run smooth and performance is good. I have 2 issues though which I suspect come from some bad configuration on my side. But I cannot figure out what it might be:

  1. Sometimes I get a “version changed. document will be reloaded” warning. And sometimes I even get a “failed to save document” warning, which prompts me to download the file to prevent data loss. This happens rarely, but regularly (once every 2 days).

  2. Documents won’t open in Safari. I only get a blank page and the top bar from Seafile. The document-server will not load. To resolve this I need to reload the User Agent in the Developer Tools within Safari. Changing the User Agent will work too, but just reloading the “Standard” option by clicking on it will suffice. This ONLY happens in Safari. Any other Browser (Chromium based and Firefox) will work just fine out of the box.

What could this be? I really don’t know how to troubleshoot this.

Greetings,
Thiemo

2

Hey Thiemo, welcome to the community!

These are two separate things, so let me break it down:

1. “Version changed” / “Failed to save”

This means Document Server tried to save back to Seafile but the connection was interrupted or Seafile didn’t respond as expected. Since it happens regularly (~every 2 days), it’s most likely a transient network issue between your Docker containers.

To figure out what’s going on:

  • How are Seafile and Document Server connected — do you have a reverse proxy in front (nginx, Caddy, Traefik, etc)? If yes, could you share the config?
  • Could you grab the DS logs from inside the container: the docservice folder + nginx.error.log from /var/log/onlyoffice/documentserver/ — zip it up, upload to Google Drive or Dropbox, and drop the link here.

2. Safari blank page

Since the Seafile top bar loads but the editor doesn’t, and everything works in Chrome/Firefox — this looks like a Seafile frontend issue rather than Document Server. You can double-check by opening https://<your-ds-address>/example/ in Safari — if the editor loads there, the DS side is fine. I’d suggest reporting this to the Seafile community as well if you haven’t already.

3

Hey there,

thanks for the quick reply.

1. “Version changed” / “Failed to save”

I am using a cloudflared tunnel (figro/unraid-cloudflared-tunnel - Docker Image) connector running as docker container. This resolves the different ports to their respective domains via published application routes. Seafile is running on port 8088; OnlyOffice on port 8083.

Rocket Loader and Cache are disabled on the used subdomains to prevent Cloudflare from caching assets.

seahub_settings.py is configured like this (this is what the installation guide suggests):

ENABLE_ONLYOFFICE = True
ONLYOFFICE_APIJS_URL = 'https://onlyoffice.example.com/web-apps/apps/api/documents/api.js'
ONLYOFFICE_JWT_SECRET = '<shared secret>'

for OnlyOffice I’ve specified these variables:

JWT_ENABLED=true 
JWT_HEADER=Authorization 
JWT_IN_BODY=true

The DS logs contain my specific domains, which I’d rather not share. I’ll post a redacted portion of the logs which I hope is representative:

in the nginx.error.log there’s only a couple of these: (all .js.map files)

2026/06/19 17:47:25 [error] 1325#1325: *11 open()
"/var/www/onlyoffice/documentserver/web-apps/vendor/underscore/underscore-umd.js.map" 
failed (2: No such file or directory), 
client: 172.20.0.1, server: , 
request: "GET /9.4.0-50d742aae35b80653a0e1f86c27ad36d/web-apps/vendor/underscore/underscore-umd.js.map HTTP/1.1", 
host: "onlyoffice-domain.example.com"

The out.log is basically only container restarts and this Object.hasOwn is not a function error:

[2026-06-19T17:31:21.828] [ERROR] [localhost] [bcf021745b9951baee8e] [userId] nodeJS - clientLog: changesError: Error: Object.hasOwn is not a function
 Script: 
 Line: :
 userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0
 platform: Win32
 isLoadFullApi: false
 isDocumentLoadComplete: false
 DocumentInfo: no logic document

err.log is empty;

all the other log files are basically just documentation of server restarts.

2. Safari blank page

I was suspecting this to be a bug within Seafile and have reported it there, too. The only thing that’s making me think it might be OnlyOffice, is the fact, that network activity stop after api.js was activated. Could be some sort of caching/timing related issue within that script, too, couldn’t it?

4

Hey @BerlinStold,

Thanks for all the details! Two things stand out:

The Object.hasOwn error — your log shows a session on Firefox 89 that crashed with Object.hasOwn is not a function. That API requires Firefox 92+ (it’s ES2022), and the log confirms the document didn’t load in that session (isDocumentLoadComplete: false). This could also be causing some of your save failures. Could you check what Firefox version is on that Windows machine where Firefox wasn’t working?

Cloudflare Tunnel + saving — since both DS and Seafile sit behind a cloudflared tunnel, all callbacks between them go through Cloudflare’s edge. Cloudflare has a ~120-second proxy read timeout by default, and WebSocket handling through tunnels can sometimes be unstable. That said, your out.log doesn’t show any callback errors from DS’s side, so if the save failures aren’t explained by the Firefox issue above, the problem might be on Seafile’s end (receiving the callback but failing to process it). Worth checking Seafile’s logs around the same time.

Safari — api.js just exposes the DocsAPI object, after that it’s Seafile’s scripts that initialize the editor. If those never fire, the break is on Seafile’s side. Good that their team is looking into it.

Start with sorting out that Firefox version, that’s the quickest win here.