Download failed... 403 forbidden

I’ve installed ONLYOFFICE Document Server to Linux. When I try to open a document in web browser editor, the editor is opened but loading of document failed. Message box shows “Download failed”. In a browser console I’ve found message:

403 Forbidden:

What is going on? Why 403? I cannot find any error in any of the server log files. What could be wrong? What shall I do now?

Please try executing the following script to fix the issue:
Let me know the results.

Hi all, I bumped into the same issue, and luckily the support helped me (many thanks). Let me describe the problem and the solution.

Environment: Ubuntu 22.04 LTS, Installation along the guidelines provided in:

a.) Same issue as above, Error “download failed”. This only happened to me, when ssl was on, it worked ok with http:// only. Verification was done just on the examples page /example

b.) I used a self signed certificate (which also seemed to be important, as naturally certificate verfication fails)

b.1) The doc service log : /var/log/onlyoffice/documentserver/docservice/out.log shows the following error:

 [2023-01-30T09:05:00.090] [ERROR] [localhost] [] [uid-11] nodeJS - changesError: Error: Uncaught TypeError: Cannot read properties of null (reading 'Tsj') Script: Line: 1530:320 userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36 platform: Win32 isLoadFullApi: false isDocumentLoadComplete: false StackTrace: TypeError: Cannot read properties of null (reading 'Tsj')   at Sb.N$g (
  at i.onDocumentContentReady (
 at i.onLongActionEnd (
 at D (
 at z.<anonymous> (
 at z.<anonymous> (
 at z.trigger (
 at (
 at Sb.iw (

As could not find any reasonable comments in the public, I contacted the support, and their recommendation was:
a.) Switch off ssl verification in /etc/onlyoffice/documentserver/default.json, i.e. search for entry “rejectUnauthorized”, change the value from true to false and restart the services by using: sudo supervisorctl restart all

On my end, this did not help, I still had an the permission issue as before. Only after running the command (as described here as well): sudo things went ok.
I do assume that self signing is key for this error, as I ran OO in a very similar environment on debian with a letsencrypt certificate and never had any such issue
Thanks for the great help of the support.
Hope this helps to save some time for others.


How do we fix this issue in windows?
Getting the same error.

This was working 2-3 days before but all of a sudden it stop working.

Create a topic already

– Rahul

Hello @rahul123mer

Please do not duplicate questions in several threads. I’ve replied to you in your thread, please keep discussion there.