Onlyoffice pptx / xlsx unknown error

Does anyone know how to solve this problem?
pptx and xlsx files do not open, showing the “unknown error” message. Only docx works normally …

Hello and3rsonlu1z,

i don’t have any problems, with editing xlsx and pptx. Please provide us more information about your environment. How was the files created? Directly with Seafile or MS-Office or …?

Hi, thanks for the reply …

Now that you mention it, I did another test with the samples from the onlyoffice community and they really open it! :slight_smile:

The problem is in new pptx or xlsx files created by seafile that do not open, showing the message unknown error … :pensive:

Hi,

ok i think this resolve your problem. Path to file is “[seafile-install-path]/seafile-server-latest/seahub/seahub/views/file.py”.
A short feedback would be nice.

Hi,
I made the changes in file.py.
Excel files are still with the “unknown error”, however .pptx now stay in “loading apresentation” …

Hi,
please give me a short description of your environment.(apache/nginx, docker? and so on )
If is possible to you please provide me the new create files, so I can test this.

Please restart Seafile and DocumentServer if you have not done it yet.

I made a gif to show happens … see that the file shows the problem is created by seafile. Other example xlsx / pptx i uploaded and it works.

My environment is with nginx / docker …

Can you share these files so we can test it on our systems? As @TMHBOFH already suggested.

I can not upload here … follow the link
https://cloud.infraops.info/d/8ca158ce8f1142c9b4c5/

I don’t know why but is not correct that new files have a size of 0 K.

any seafile logs?

Seeing the seahub.log I noticed this the below every time I create a docx, pptx or xlsx file.

Other file types do not display the error.

Seahub.log
2017-06-04 23:23:54,581 [ERROR] seahub.api2.endpoints.file:193 post HTTPSConnectionPool(host='cloud.infraops.info', port=443): Max retries exceeded with url: /seafhttp/update-api/7b78aa8e-9adf-40ac-b935-d030233d75be (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f9aa5072c90>: Failed to establish a new connection: [Errno 111] Connection refused',)) 2017-06-04 23:24:17,752 [ERROR] seahub.api2.endpoints.file:193 post HTTPSConnectionPool(host='cloud.infraops.info', port=443): Max retries exceeded with url: /seafhttp/update-api/ce3377c5-4501-459f-b1d9-644e6b24af51 (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f9aa506f310>: Failed to establish a new connection: [Errno 111] Connection refused',)) 2017-06-04 23:24:25,091 [ERROR] seahub.api2.endpoints.file:193 post HTTPSConnectionPool(host='cloud.infraops.info', port=443): Max retries exceeded with url: /seafhttp/update-api/5434be67-e18b-4328-8a2b-dc110fdd40a5 (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f9aa5083050>: Failed to establish a new connection: [Errno 111] Connection refused',))

I checked nginx and seafhttp location looks like this:

location /seafhttp {
	rewrite ^/seafhttp(.*)$ $1 break;
	proxy_pass http://127.0.0.1:8082;
}

Hello,
I have the same error with the new excel or powerpoint files.
I have nothing in the logs.
Have you solved this problem?

Just tested locally, everything works fine.
Did you setup the OnlyOffice DS according to the manual I wrote?
Also think about to update the docker image.

https://manual.seafile.com/deploy/only_office.html

Does your server have access to the host cloud.infraops.info:443?
It may be blocked by firewall or something.

The local test is ok https: //seafileoffice.*****/onlyofficeds/welcome/
Deployment of DocumentServer via SUBFOLDER
I followed your manual to setup OnlyOffice and everything went well.
I also noticed that the newly created files are at 0 byte.

Maybe a problem with access rights?

Docker version:
Customer:
Version: 17.05.0-ce
API version: 1.29
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:12:14 2017
OS / Arch: linux / amd64

Server:
Version: 17.05.0-ce
API version: 1.29 (minimum version 1.12)
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:12:14 2017
OS / Arch: linux / amd64
Experimental: false

I have this error in ngninx logs:

2017/06/26 16:09:09 [error] 6117 # 0: * 424 recv () failed (104: Connection reset by peer) while reading response header from upstream, client: 172.17.83.14, server: seafileoffice.**********. GET / onlyofficeds / 2017-06-09-10-21 / doc / 03bfe7f131a8c6ad9303 / c / info? T = 1498486147947 HTTP / 1.1 ", upstream:" http://127.0.0.1:88/2017- Host: "seafileoffice.***********", referrer: "https://seafileoffice.**********/onlyofficeds/2017-06-doc / 03bfe7f131a8c6ad9303 / c / info? T = 1498486147947" 09-10-21 / web-apps / apps / spreadsheeteditor / main / index.html? _dc 2017-06-09-10-21 = & lang = en & customer = onlyoffice & frameEditorId = placeholder "

Thanks

What did you configure in Seafile?
Is your certificate valid?

I left the default configuration of seafile in SSL
The certificate is valid.
This is what I have for the site in nginx:

Location / seafhttp {
         Rewrite ^ / seafhttp (. *) $ $ 1 break;
         Proxy_pass http://127.0.0.1:8082;
         Client_max_body_size 0;
         Proxy_connect_timeout 36000s;
         Proxy_read_timeout 36000s;
         Proxy_send_timeout 36000s;
         Send_timeout 36000s;
}

I mean your Seafile config regarding onlyoffice and the part of your nginx config regarding onlyoffice.

Sorry, here is my configuration in nginx for OpenOffice.
Thank you for your help.

location /onlyofficeds/ {
# IMPORTANT ! - Trailing slash !
proxy_pass http://127.0.0.1:88/;

    proxy_http_version 1.1;
    client_max_body_size 100; # Limit Document size to 100MB
    proxy_read_timeout 3600s;
    proxy_connect_timeout 3600s;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $proxy_connection;

    # IMPORTANT ! - Subfolder and NO trailing slash !
    proxy_set_header X-Forwarded-Host $the_host/onlyofficeds;

    proxy_set_header X-Forwarded-Proto $the_scheme;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

Change to client_max_body_size 100M;

service nginx reload

Try again.