ONLYOFFICE and ownCloud 10.15 Error ("Error occurred in the document service: Error while downloading the document file to be converted.) (version 8.3.1.25)")

Type of installation of the Document Server (docker, deb/rpm, exe, please point us to the installation guide that you used as well): Docker. I used the ONLYOFFICE guide here: Installing ONLYOFFICE Docs for Docker on a local server

Connector version: Latest from ownCloud Marketplace.

DMS (platform) version: ownCloud 10.15.0.2

OS: Docker/Ubuntu 24 (Host: macOS Sequoia 15.3.1)

Browser version: Safari 18.3 and Firefox 136 (64-bit)

Additional information:

ownCloud and ONLYOFFICE operate on separate physical servers behind the same public IP. Each has different port assignments and is accessible to the other via public IP:port and local IP:port, as well as domain name:port.

I created my own JWT during install and it is reflected in ONLYOFFICE files.

ownCloud: https : //subdomain1[dot]domain[dot]com:443
ONLYOFFICE: https : //subdomain2[dot]domain[dot]com:440

When attempting to use ownCloud Connector, I input the domain:port for ONLYOFFICE and my JWT. Instead of moving on to Editor settings, I get this error: “Error occurred in the document service: Error while downloading the document file to be converted.) (version 8.3.1.25)”

Any help is appreciated!

Should also note that both servers have Let’s Encrypt-issued SSL certs.

Most recent ONLYOFFICE Docker log is below. I don’t understand the 1981 references—maybe a clue?

2025-03-13 22:17:32 [2025-03-14T02:17:32.605] [ERROR] [localhost] [check_445603656] [userId] nodeJS - error downloadFile:url=https://subdomain1.domain.com/owncloud/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.6mCv8ZtmL10hNi5Uake6vWoKqgtjRVLcyR_LNdAXm9w;attempt=3;code:null;connect:null Error: Error response: statusCode:403; headers:{"date":"Fri, 14 Mar 2025 02:17:32 GMT","server":"Apache/2.4.63 (Unix) OpenSSL/3.4.1 PHP/7.4.33","strict-transport-security":"max-age=15552000; includeSubDomains","x-powered-by":"PHP/7.4.33","set-cookie":["ocoz8x8tz0hu=1sfk1qn1rstkclmae6mnqqh5a1; path=/owncloud; secure; HttpOnly","oc_sessionPassphrase=7iigBg%2FDrCLiBIJFwgAAvPvrrCz4rCrU76yTak%2FJbnw%2BUSTxE0kPugjdCZzd%2Bq976mbzTbM%2FNPmxjwgM58368fP8cVCJKzGK5KuT3FAH%2FDX86BL2vDbvGkcUKmOUJV2S; expires=Fri, 14-Mar-2025 02:37:32 GMT; Max-Age=1200; path=/owncloud; secure; HttpOnly; SameSite=Strict"],"expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-cache, no-store, must-revalidate","pragma":"no-cache","content-security-policy":"default-src 'none';manifest-src 'self';script-src 'self' 'unsafe-eval';style-src 'self' 'unsafe-inline';img-src 'self' data: blob:;font-src 'self';connect-src 'self';media-src 'self'","x-xss-protection":"0","x-content-type-options":"nosniff","x-frame-options":"SAMEORIGIN","x-robots-tag":"none","x-download-options":"noopen","x-permitted-cross-domain-policies":"none","content-length":"27","keep-alive":"timeout=3, max=200","connection":"Keep-Alive","content-type":"application/json; charset=utf-8"};
2025-03-13 22:17:32     at Request.fResponse (/snapshot/server/Common/sources/utils.js)
2025-03-13 22:17:32     at Request.emit (node:events:527:28)
2025-03-13 22:17:32     at Request.onRequestResponse (/snapshot/server/Common/node_modules/request/request.js:1066:10)
2025-03-13 22:17:32     at ClientRequest.emit (node:events:527:28)
2025-03-13 22:17:32     at HTTPParser.parserOnIncomingClient (node:_http_client:631:27)
2025-03-13 22:17:32     at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
2025-03-13 22:17:32     at TLSSocket.socketOnData (node:_http_client:494:22)
2025-03-13 22:17:32     at TLSSocket.emit (node:events:527:28)
2025-03-13 22:17:32     at addChunk (node:internal/streams/readable:315:12)
2025-03-13 22:17:32     at readableAddChunk (node:internal/streams/readable:289:9)
2025-03-13 22:17:32     at TLSSocket.Readable.push (node:internal/streams/readable:228:10)
2025-03-13 22:17:32     at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)
2025-03-14 02:54:00 tail: /var/log/onlyoffice/documentserver/nginx.error.log: file truncated
2025-03-14 02:54:00 tail: /var/log/onlyoffice/documentserver/converter/out.log: file truncated
2025-03-14 02:54:00 tail: /var/log/onlyoffice/documentserver/docservice/out.log: file truncated

Also, FWIW, I’ve confirmed both machines’ clocks are in sync.

Hello @cjh_dc

Thank you for providing logs of Document Server. As I can see, you are getting status code 403 that indicates to following possible issues:

  • JWT credentials (secret/header) that are used in the connector app settings are incorrect;
  • the securelink value has not been updated after turning SSL on;
  • problem with SSL certificates.

Firstly, it is important to check out whether Document Server works accordingly. You can do it by opening Document Server via its address, enabling integrated test example as per instruction on the Welcome page, then opening integrated test example itself to create/upload any documents for editing. Once any document is created/uploaded, open it for editing to see if the editor reports any errors.

Secondly, you can run through the possible issues that I’ve mentioned to see if any of them is causing the problem:

  • check JWT credentials in local.json file inside the container with Document Server in directory /etc/onlyoffice/documentserver. If used in connector app settings credentials are correct, move to the next step.
    Note: If you previously changed credentials in local.json make sure that Document Servers’ services were restarted and new values are applied with command supervisorctl restart all;
  • to make sure that securelink value is synced correctly, please run bash /usr/bin/documentserver-update-securelink.sh command inside the container with Document Server and then check if the same error is reported when attempting to connect Document Server to ownCloud via connector app;
  • if there is an issue with applied SSL certificates, please try setting up rejectUnauthorized parameter to false in default.json config in the same directory and restarting Document Servers’ services with above mentioned command.

If none of these steps help, please try connecting again and check out latest logs again.


To connect to the running container with Document Server use docker exec -it <ID> bash, where <ID> is the ID of container with Document Server. You can find ID by running docker ps command.

Hi Constantine,

Thanks so much for the thoughtful reply. I appreciate your help!

I’ve followed each of the steps you suggested and have also updated my trusted domains in ownCloud to include subdomain1[dot]domain[dot]com, subdomain2[dot]domain[dot]com, domain[dot]com, www[dot]domain[dot]com, and *[dot]domain[dot]com.

Unfortunately, my error message hasn’t changed, and (at least to my eyes), the log looks the same, too.

2025-03-18 09:59:38 [2025-03-18T13:59:38.674] [ERROR] [localhost] [check_1448114779] [userId] nodeJS - error downloadFile:url=https://subdomain1.domain.com/owncloud/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.6mCv8ZtmL10hNi5Uake6vWoKqgtjRVLcyR_LNdAXm9w;attempt=3;code:null;connect:null Error: Error response: statusCode:403; headers:{"date":"Tue, 18 Mar 2025 13:59:38 GMT","server":"Apache/2.4.63 (Unix) OpenSSL/3.4.1 PHP/7.4.33","strict-transport-security":"max-age=15552000; includeSubDomains","x-powered-by":"PHP/7.4.33","set-cookie":["ocoz8x8tz0hu=brde3bcrjbtgfgvgcrsdffej7r; path=/owncloud; secure; HttpOnly","oc_sessionPassphrase=yIZuS7xGgKQi9TmFtY0PnzlJKGl38EbvMNB3MQZALTViz6YFNyqBjaY9MhKL3R0lltPKtCt4EAruj5dMwtLqsrc34R9Z1fbSJtp5TSssUTWIVIWcVpaVER%2B%2B2booFXRR; expires=Tue, 18-Mar-2025 14:19:38 GMT; Max-Age=1200; path=/owncloud; secure; HttpOnly; SameSite=Strict"],"expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-cache, no-store, must-revalidate","pragma":"no-cache","content-security-policy":"default-src 'none';manifest-src 'self';script-src 'self' 'unsafe-eval';style-src 'self' 'unsafe-inline';img-src 'self' data: blob:;font-src 'self';connect-src 'self';media-src 'self'","x-xss-protection":"0","x-content-type-options":"nosniff","x-frame-options":"SAMEORIGIN","x-robots-tag":"none","x-download-options":"noopen","x-permitted-cross-domain-policies":"none","content-length":"27","keep-alive":"timeout=3, max=200","connection":"Keep-Alive","content-type":"application/json; charset=utf-8"};
2025-03-18 09:59:38     at Request.fResponse (/snapshot/server/Common/sources/utils.js)
2025-03-18 09:59:38     at Request.emit (node:events:527:28)
2025-03-18 09:59:38     at Request.onRequestResponse (/snapshot/server/Common/node_modules/request/request.js:1066:10)
2025-03-18 09:59:38     at ClientRequest.emit (node:events:527:28)
2025-03-18 09:59:38     at HTTPParser.parserOnIncomingClient (node:_http_client:631:27)
2025-03-18 09:59:38     at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
2025-03-18 09:59:38     at TLSSocket.socketOnData (node:_http_client:494:22)
2025-03-18 09:59:38     at TLSSocket.emit (node:events:527:28)
2025-03-18 09:59:38     at addChunk (node:internal/streams/readable:315:12)
2025-03-18 09:59:38     at readableAddChunk (node:internal/streams/readable:289:9)
2025-03-18 09:59:38     at TLSSocket.Readable.push (node:internal/streams/readable:228:10)
2025-03-18 09:59:38     at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)

Forgot to add—using the integrated example worked just fine with no error messages on doc creation or save.

Thank you for the reply. Please try using wget <owncloud_address> from the server with Document Server to see what it returns. Just in case, do the same but vice versa, i.e. from the server with ownCloud to Document Server. Let me know what the result is.

Connecting to ownCloud server from server running ONLYOFFICE:

user@onlyoffice ~ % wget https://subdomain1[dot]domain[dot]com:443/owncloud/index.php
--2025-03-20 16:54:53--  https://subdomain1[dot]domain[dot]com/owncloud/index.php
Resolving subdomain1[dot]domain[dot]com (subdomain1[dot]domain[dot]com)... 12.34.56.78
Connecting to subdomain1[dot]domain[dot]com (subdomain1[dot]domain[dot]com)|12.34.56.78|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://subdomain1[dot]domain[dot]com/owncloud/index.php/login [following]
--2025-03-20 16:54:53--  https://subdomain1[dot]domain[dot]com/owncloud/index.php/login
Reusing existing connection to subdomain1[dot]domain[dot]com:443.
HTTP request sent, awaiting response... 200 OK
Length: 11391 (11K) [text/html]
Saving to: ‘index.php’

index.php           100%[===================>]  11.12K  --.-KB/s    in 0s      

2025-03-20 16:54:53 (45.1 MB/s) - ‘index.php’ saved [11391/11391]

Connecting to ONLYOFFICE server from ownCloud server:

user@owncloud ~ % wget https://subdomain2[dot]domain[dot]com:440
--2025-03-20 16:57:35--  https://subdomain2[dot]domain[dot]com:440/
Resolving subdomain2[dot]domain[dot]com (subdomain2[dot]domain[dot]com)... 12.34.56.78
Connecting to subdomain2[dot]domain[dot]com (subdomain2[dot]domain[dot]com)|12.34.56.78|:440... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://subdomain2[dot]domain[dot]com:440/welcome/ [following]
--2025-03-20 16:57:35--  https://subdomain2[dot]domain[dot]com:440/welcome/
Reusing existing connection to subdomain2[dot]domain[dot]com:440.
HTTP request sent, awaiting response... 200 OK
Length: 4948 (4.8K) [text/html]
Saving to: ‘index.html.1’

index.html.1        100%[===================>]   4.83K  --.-KB/s    in 0s      

2025-03-20 16:57:35 (4.61 GB/s) - ‘index.html.1’ saved [4948/4948]

Thanks. I’d recommend changing the default JWT header to something else. For instance, try setting it up in local.json as AuthorizationJwt:

        "inbox": {
          "header": "AuthorizationJwt",
          "inBody": false
        },
        "outbox": {
          "header": "AuthorizationJwt",
          "inBody": false
        }

Then restart Document Server services and try connecting Document Server again with this new header in advanced settings.

Thanks for the suggestion. That did the trick! At first, local.json didn’t save with changes in my Docker install, but the second attempt got us there. Thanks again very much for your help!

1 Like

I am glad to know that it helped.