OnlyOffice Docs not Opening

[SushantRathore-Admin]

Hi Team,

I have installed Onlyoffice on oracle 7 Linux using this doc https://helpcenter.onlyoffice.com/installation/docs-enterprise-install-centos.aspx.

It's working fine but after disabling the SELinux docs are not opening.

Thanks

[ShockwaveNN]

Hi, describe in more details that is

docs are not opening.

Is there any error in interface and what are errors in /var/log/onlyoffice

Usually enabling SELinux cause trouble, not disabling it

[SushantRathore-Admin]

Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.0.0.132)

Hi, describe in more details that is

docs are not opening.

Is there any error in interface and what are errors in /var/log/onlyoffice

Usually enabling SELinux cause trouble, not disabling it

Hi,

Thanks for reply , Now i m trying to connect onlyoffice with nextcloud facing this issues.

Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.0.0.132)

tail -f /var/log/onlyoffice/documentserver/converter/out.log Here are logs 👍

[2022-03-05T03:44:59.661] [ERROR] nodeJS - error downloadFile:url=https://office.exadime.com/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.NDLWYzgkeldFUGRG7ez_vV3cZpIzXR0CqIOJWHNYWQU;attempt=3;code:null;connect:null;(id=conv_check_1613955113_docx)
Error: Error response: statusCode:404; headers:{"server":"nginx","date":"Sat, 05 Mar 2022 08:44:59 GMT","content-type":"text/html; charset=utf-8","transfer-encoding":"chunked","connection":"keep-alive","vary":"Accept-Encoding","x-powered-by":"Express","content-security-policy":"default-src 'none'","x-content-type-options":"nosniff","content-encoding":"gzip"};
    at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js)
    at Request.emit (events.js:400:28)
    at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10)
    at ClientRequest.emit (events.js:400:28)
    at HTTPParser.parserOnIncomingClient (_http_client.js:647:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
    at TLSSocket.socketOnData (_http_client.js:515:22)
    at TLSSocket.emit (events.js:400:28)
    at addChunk (internal/streams/readable.js:290:12)
    at readableAddChunk (internal/streams/readable.js:265:9)
    at TLSSocket.Readable.push (internal/streams/readable.js:204:10)
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

Thanks

[ShockwaveNN]

Do you use some kind proxy between DocumentServer and Nextcloud?

I think this error mean something wrong in connection between those services

Could you try DocumentServer integrated example (instruction how to turn on located at http://docserverurl/welcome) and see if DocumentServer works fine by itself and if so - problem in network layer somewhere

[SushantRathore-Admin]

example

Thanks for you quick response,

I tried as you suggested

When i m using https://office.exadime.com/welcome getting error 404 as given in below.

Error when trying to connect (Client error: GET https://office.exadime.com/welcome/healthcheck resulted in a 404 Not Found response:

404 Not Found

404 Not Found nginx

When i m trying https://office.exadime.com/example getting healthcheckresulted in a404 Not Found as given in below.

Error when trying to connect (Client error: GET https://office.exadime.com/example/healthcheck resulted in a 404 Not Found response:

[ShockwaveNN]

If you get 404 on welcome seems that Nginx is not correctly setup

Do you not forget the last step of this instruction

bash documentserver-configure.sh

If not - you didn't answer is there any proxy? And if there is - I think this is a problem

Alternatively you can try to use docker version - it's much easier to setup

[SushantRathore-Admin]

If you get 404 on welcome seems that Nginx is not correctly setup

Do you not forget the last step of this instruction

bash documentserver-configure.sh

If not - you didn't answer is there any proxy? And if there is - I think this is a problem

Alternatively you can try to use docker version - it's much easier to setup

I used bash documentserver-configure.sh command.

If not - you didn't answer is there any proxy? And if there is - I think this is a problem --> I not sure about it but mainly i used installations doc https://helpcenter.onlyoffice.com/installation/docs-enterprise-install-centos.aspx as they mentions i did all these steps one by one., ever onlyoffice server working fine but facing issues while connecting from nextcloud.

[ShockwaveNN]

I do not understand

You mention that server is working fine but you get 404 on welcome

This is not right

When i m using https://office.exadime.com/welcome get error 404 as given in below. Error when trying to connect (Client error: GET https://office.exadime.com/welcome/healthcheck resulted in a 404 Not Found response:

Why is there welcome/healcheck in URL? It should be https://office.exadime.com/healthcheck

And same for https://office.exadime.com/example/healthcheck

Also please try to format your responses correctly, it is very hard to read then it is just a combination of your and my words

[SushantRathore-Admin]

https://office.exadime.com/healthcheck

If i m trying to hit https://office.exadime.com/healthcheck getting output true so its working fine.

But when i m trying to hit (https://office.exadime.com/ its redirecting to (https://office.exadime.com/welcome then onlyofffice welcome pages are opening.

[ShockwaveNN]

But when i m trying to hit (https://office.exadime.com/ its redirecting to (https://office.exadime.com/welcome then onlyofffice welcome pages are opening.

Yes this is right behavior

[SushantRathore-Admin]

But when i m trying to hit (https://office.exadime.com/ its redirecting to (https://office.exadime.com/welcome then onlyofffice welcome pages are opening.

Yes this is right behavior

Ok if this is right behaver then what i need to do for connecting it from nextcloud. Because when i m hitting my domain from nextcloud its searching healthcheck file inside domain-name/welcome/healthcheck.

If i m hitting domainname/welcome then getting below error Please check Nginx logs here -

2022/03/05 03:43:05 [error] 1221#1221: *121 connect() failed (111: Connection refused) while connecting to upstream, client: 10.0.1.226, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://[::1]:8000/favicon.ico", host: "office.exadime.com", referrer: "https://office.exadime.com/example/editor?fileName=new.docx" 2022/03/05 03:43:08 [error] 1221#1221: *121 connect() failed (111: Connection refused) while connecting to upstream, client: 10.0.1.226, server: , request: "GET /example/ HTTP/1.1", upstream: "http://[::1]:3000/", host: "office.exadime.com", referrer: "https://office.exadime.com/welcome/" 2022/03/05 03:43:08 [error] 1221#1221: *121 connect() failed (111: Connection refused) while connecting to upstream, client: 10.0.1.226, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://[::1]:8000/favicon.ico", host: "office.exadime.com", referrer: "https://office.exadime.com/example/" 2022/03/05 03:43:17 [error] 1221#1221: *121 connect() failed (111: Connection refused) while connecting to upstream, client: 10.0.1.226, server: , request: "GET /example/ HTTP/1.1", upstream: "http://[::1]:3000/", host: "office.exadime.com", referrer: "https://office.exadime.com/welcome/" 2022/03/05 03:43:17 [error] 1221#1221: *121 connect() failed (111: Connection refused) while connecting to upstream, client: 10.0.1.226, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://[::1]:8000/favicon.ico", host: "office.exadime.com", referrer: "https://office.exadime.com/example/" 2022/03/05 07:21:21 [error] 1221#1221: *502 open() "/var/www/onlyoffice/documentserver-example/welcome/healthcheck" failed (2: No such file or directory), client: 10.0.0.40, server: , request: "GET /welcome/healthcheck HTTP/1.1", host: "office.exadime.com"

If i m hittying only domain like https://office.exadime.com then getting Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.0.0.132)✖

please see error [2022-03-05T09:01:17.977] [ERROR] nodeJS - error downloadFile:url=https://office.exadime.com/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.NDLWYzgkeldFUGRG7ez_vV3cZpIzXR0CqIOJWHNYWQU;attempt=1;code:null;connect:null;(id=conv_check_728234540_docx) Error: Error response: statusCode:404; headers:{"server":"nginx","date":"Sat, 05 Mar 2022 14:01:17 GMT","content-type":"text/html; charset=utf-8","transfer-encoding":"chunked","connection":"keep-alive","vary":"Accept-Encoding","x-powered-by":"Express","content-security-policy":"default-src 'none'","x-content-type-options":"nosniff","content-encoding":"gzip"}; at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js) at Request.emit (events.js:400:28) at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:265:9) at TLSSocket.Readable.push (internal/streams/readable.js:204:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23) [2022-03-05T09:01:18.996] [ERROR] nodeJS - error downloadFile:url=https://office.exadime.com/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.NDLWYzgkeldFUGRG7ez_vV3cZpIzXR0CqIOJWHNYWQU;attempt=2;code:null;connect:null;(id=conv_check_728234540_docx) Error: Error response: statusCode:404; headers:{"server":"nginx","date":"Sat, 05 Mar 2022 14:01:18 GMT","content-type":"text/html; charset=utf-8","transfer-encoding":"chunked","connection":"keep-alive","vary":"Accept-Encoding","x-powered-by":"Express","content-security-policy":"default-src 'none'","x-content-type-options":"nosniff","content-encoding":"gzip"}; at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js) at Request.emit (events.js:400:28) at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:265:9) at TLSSocket.Readable.push (internal/streams/readable.js:204:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23) [2022-03-05T09:01:20.015] [ERROR] nodeJS - error downloadFile:url=https://office.exadime.com/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.NDLWYzgkeldFUGRG7ez_vV3cZpIzXR0CqIOJWHNYWQU;attempt=3;code:null;connect:null;(id=conv_check_728234540_docx) Error: Error response: statusCode:404; headers:{"server":"nginx","date":"Sat, 05 Mar 2022 14:01:20 GMT","content-type":"text/html; charset=utf-8","transfer-encoding":"chunked","connection":"keep-alive","vary":"Accept-Encoding","x-powered-by":"Express","content-security-policy":"default-src 'none'","x-content-type-options":"nosniff","content-encoding":"gzip"}; at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js) at Request.emit (events.js:400:28) at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:265:9) at TLSSocket.Readable.push (internal/streams/readable.js:204:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)

[ShockwaveNN]

Could you show nextcloud connector settings page?

[SushantRathore-Admin]

Could you show nextcloud connector settings page? Nextcloud connector settings page, is this one or anything else ?

[ShockwaveNN]

I'm not very good at nextcloud, but seems right for

One last question from me

When you've opening https://office.exadime.com/example/ URL - opening documents and saving them via integrated example is fine? And only troubles you get - with nextcloud integration

Am I right?

[SushantRathore-Admin]

I'm not very good at nextcloud, but seems right for

One last question from me

When you've opening https://office.exadime.com/example/ URL - opening documents and saving them via integrated example is fine? And only troubles you get - with nextcloud integration

Am I right?

yes You are right, only facing issues while doing integration with nextcloud. if i will open https://office.exadime.com/example/ that is working file can edit doc write as well.

[ShockwaveNN]

In that case I'll redirect this issue to people who work with nextcloud

[SushantRathore-Admin]

In that case I'll redirect this issue to people who work with nextcloud

Sure please redirect because we want to put it in productions.

[SergeyKorneyev]

Hi @SushantRathore-Admin As far as I know, the issue has been fixed on our forum. Could you close it here, if that's the case?

[bugbountyguy]

I know this is an old issue, but...

I just updated to the latest version of the Onlyoffice version on Nextcloud today and started to receive 404's for this /empty?doc=.... URL as well. I am personally behind a reverse proxy, but haven't made any config updates to it in like a year, so doubt that's it.

I was able to temporarily get around this by manually editing /custom_apps/onlyoffice/lib/DocumentService.php by commenting out lines 457-462:

        #try {
        #    $this->Request($convertedFileUri);
        #} catch (\Exception $e) {
        #    $logger->logException($e, ["message" => "Request converted file on check error", "app" => self::$appName]);
        #    return [$e->getMessage(), $version];
        #}

Clicked save in the OnlyOffice settings and then was able to open/edit files like before the update. It seems using this as a way to check on whether the application can work or not is not a valid way to do it.

Hopefully this helps anyone else running into this issue, and maybe the devs to find a better way to check whether the app will work on a system.

If it helps at all, I've got a custom Docker setup, reverse nginx proxy, ONLYOFFICE 8.2.0, and NC 27.0.2.

[wedreamer]

I know this is an old issue, but...

I just updated to the latest version of the Onlyoffice version on Nextcloud today and started to receive 404's for this /empty?doc=.... URL as well. I am personally behind a reverse proxy, but haven't made any config updates to it in like a year, so doubt that's it.

I was able to temporarily get around this by manually editing /custom_apps/onlyoffice/lib/DocumentService.php by commenting out lines 457-462:

        #try {
        #    $this->Request($convertedFileUri);
        #} catch (\Exception $e) {
        #    $logger->logException($e, ["message" => "Request converted file on check error", "app" => self::$appName]);
        #    return [$e->getMessage(), $version];
        #}

Clicked save in the OnlyOffice settings and then was able to open/edit files like before the update. It seems using this as a way to check on whether the application can work or not is not a valid way to do it.

Hopefully this helps anyone else running into this issue, and maybe the devs to find a better way to check whether the app will work on a system.

If it helps at all, I've got a custom Docker setup, reverse nginx proxy, ONLYOFFICE 8.2.0, and NC 27.0.2.

This causes the request to not be sent, resulting in the requester eventually receiving a timeout exception

==> /var/log/onlyoffice/documentserver/nginx.error.log <==
2023/09/08 08:52:51 [error] 7045#7045: *71 upstream timed out (110: Unknown error) while reading response header from upstream, client: 172.19.0.4, server: , request: "POST /ConvertService.ashx HTTP/1.1", upstream: "http://127.0.0.1:8000/ConvertService.ashx", host: "onlyoffice"

==> /var/log/onlyoffice/documentserver/converter/out.log <==
[2023-09-08T08:53:51.403] [ERROR] [localhost] [conv_check_1368899331_docx] [userId] nodeJS - error downloadFile:url=http://nextcloud.shubuzuo.top:8080/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.ja0BttCk7c97EDL_LBUiDSyAL-DJn6I-wkjHeL3R_SI;attempt=1;code:ETIMEDOUT;connect:undefined Error: Error: whole request cycle timeout
    at raiseError (/snapshot/server/build/server/Common/sources/utils.js)
    at Timeout._onTimeout (/snapshot/server/build/server/Common/sources/utils.js)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)

==> /var/log/onlyoffice/documentserver/nginx.error.log <==
2023/09/08 08:53:58 [error] 7045#7045: *77 upstream timed out (110: Unknown error) while reading response header from upstream, client: 172.19.0.4, server: , request: "POST /ConvertService.ashx HTTP/1.1", upstream: "http://127.0.0.1:8000/ConvertService.ashx", host: "onlyoffice"