Onlyoffice/documentserver 9.4.x does not work within NC with ONLYOFFICE 10.0.0 app enabled

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 33.0.3
  • Operating system and version (e.g., Ubuntu 24.04):
    • ubuntu 24.04
  • Web server and version (e.g, Apache 2.4.25):
    • NGinx
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • NGinx
  • PHP version (e.g, 8.3):
    • 8.4.21
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • after pulling documentserver(latest)
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • docker
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

I have a script that is updating my ONLYOFFICE (docker) with the latest (stable)

two times per month. The latest version i s 9.4.0.1

I can reach my ONLYOFFICE by url OO-FQDN:443 or NC-FQDN:8443 without issues.
The “connector” (ONLYOFFICE App is 10.0.0 from the nextcloud app store) and a self test says connection established (green tag)

When opening documents i get a blank page (word) or a blank table (calc)

With new docs the same.

My ONLYOFFICE docker container resides on the nextcloud server (192.168.55.16)

Steps to replicate it (hint: details matter!):

  1. update docker image for onlyoffice documentserver from 9.3.x to latest(9.4.x)

  2. downgrade to a lower version e.g. with docker pull onlyoffice/documentserver:9.3.1.2

  3. restart docker and container, restart nginx (php), reconnect to nextcloud and see that docs can be edited as expected!

  4. seems that ONLYOFFICE App can no longer make onlyoffice/documentserver docker accessible within nextcloud? Can anyone confirm?

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

I get the following errors

Error with Feature-Policy header: Some features are specified in both Feature-Policy and Permissions-Policy header: camera, geolocation, microphone, payment. Values defined in Permissions-Policy header will be used.

Error with Permissions-Policy header: Unrecognized feature: 'browsing-topics'.

The FetchEvent for "https://OO-FQDN/9.4.0-ff36968…/web-apps/apps/common/Analytics.js" resulted in a network error response: the promise was rejected.

document_editor_service_worker.js:339 
 Uncaught (in promise) TypeError: Failed to fetch
    at document_editor_service_worker.js:339:21

require.js:1961 
 GET https://OO-FQDN/9.4.0-ff36968…/web-apps/apps/common/Analytics.js net::ERR_FAILED

and from docker logs -f ONLYOFFICE i get

==> /var/log/onlyoffice/documentserver/nginx.error.log <==
2026/05/20 11:01:09 [error] 11215#11215: *34 open() “/var/www/onlyoffice/documentserver/web-apps/vendor/socketio/socket.io.min.js.map” failed (2: No such file or directory), client: 192.168.55.90, server: , request: “GET /9.4.0-ff369681c3b817a16611f2fa73d6b42a/web-apps/vendor/socketio/socket.io.min.js.map HTTP/1.0”, host: “OO-FQDN”
2026/05/20 11:01:09 [error] 11215#11215: *33 open() “/var/www/onlyoffice/documentserver/web-apps/vendor/underscore/underscore-umd.js.map” failed (2: No such file or directory), client: 192.168.55.90, server: , request: “GET /9.4.0-ff369681c3b817a16611f2fa73d6b42a/web-apps/vendor/underscore/underscore-umd.js.map HTTP/1.0”, host: “OO-FQDN”

192.168.55.90 is my reverse proxy (Nginx)

the nginx conf for ONLYOFFICE is

server {
        listen 443 ssl;
        
        # see: https://codefaq.org/server/how-to-address-the-deprecation-of-the-listen-http2-directive-in-nginx/
        http2 on;

        server_name OO-FQDN;

        
		# SSL Config for all redirected Target URLs
		ssl_certificate /etc/letsencrypt/ecc-cert/fullchain.pem;
		ssl_certificate_key /etc/letsencrypt/ecc-cert/privkey.pem;
		ssl_trusted_certificate /etc/letsencrypt/ecc-cert/chain.pem;

	    ssl_dhparam /etc/nginx/ssl/dhparam.pem;
		ssl_session_timeout 1d;
		ssl_session_cache shared:SSL:50m;
		ssl_session_tickets off;
   		
		ssl_protocols TLSv1.2 TLSv1.3;
   		# Framing-Prevention - do not use this URL for Phishing / Framing
		ssl_ciphers 'TLS-CHACHA20-POLY1305-SHA256:TLS-AES-256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384';
	    ssl_ecdh_curve X448:secp521r1:secp384r1:prime256v1;
	    
		ssl_prefer_server_ciphers on;

		set $upstream 192.168.55.16;
        #
        # Configuration for OnlyOffice
        #
        location / {
			proxy_pass https://$upstream:8443;
            proxy_redirect off;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Host $server_name;
            proxy_set_header X-Forwarded-Proto $scheme;
			proxy_set_header Upgrade $http_upgrade;
        }
}

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

The script that is pulling my ONLYOFFICE docker image is

#!/bin/bash
#
docker stop ONLYOFFICE
docker rm ONLYOFFICE
docker image rm $(docker image ls | grep onlyoffice/documentserver | awk '{ print $3 }')
docker system prune -a -f
#
docker pull onlyoffice/documentserver:9.3.1.2
#
cat /etc/letsencrypt/rsa-certs/privkey.pem > /app/onlyoffice/DocumentServer/data/certs/onlyoffice.key
cat /etc/letsencrypt/rsa-certs/fullchain.pem > /app/onlyoffice/DocumentServer/data/certs/onlyoffice.crt
echo "Starte neuen Container ONLYOFFICE; Portmapping 8443:443"
#
docker run --name=ONLYOFFICE -i -t -d -p 8443:443 --restart=always --add-host=NC_FQDN:192.168.55.16 \
    -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data \
    -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice  \
    -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice \
    -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql \
    -e JWT_ENABLED='true' -e JWT_SECRET='MY_SECRET' onlyoffice/documentserver:9.3.1.2
#
# restart services
systemctl restart php8.4-fpm && systemctl restart nginx && systemctl restart postgresql
exit 0

usually i am pulling pull onlyoffice/documentserver (for latest) but for now i switched to a fixed version (9.3.1.2)

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

Corresponding issue report on github …

and here