Seafile-onlyoffice download error


#1

Hello,

I have two servers seafile and onlyoffice. this servers over http works like they have to work.
i switched both servers to https, but when i open a file i get download error, document cant be saved.

i tested docuemnt server using example erver and works good, but when i try to integratewith seafile i get this error.

Maybe someone know something about this?

Thanks a lot


#2

Do you have configure https in your SERVICE_URL and seahub_settings.py?


#3

well i configured SERVICE_URL in ccnet.conf and HTTP_SERVER_ROOT in seahub_setting.py. actually i can upload and download docuement in seafile. the error happens when open a document to edit with onlyoffice


#4

You now that they are stored in the DB after first start? Have you deleted the DB entries first? Otherwise, I suggest changing the DB via Admin Panel.


#5

you mean delete entries beacuse changing from HTTP to https?
Well they are stored because i configured from webadmin panel and persist…


#6

so you already changed them to https in the WebUI. Do you use subdomain or folder?
Have you changed ONLYOFFICE_APIJS_URL?


#7

yes i did, im using subdomain.


#8

Have you changed ONLYOFFICE_APIJS_URL?
Do you have a cert for the subdomain (sorry if this is a stupid question)?


#9

yes, i changed apis url, actually onlyoffice open when click in a docuement. but when loading its returns and error saying download error. codument cant be saved…
yes both servers have certs.
i think is a negotiton problem or im missing a config.


#10

I sometimes have the problem, that sf and OO don’t link. Solution is to restart OO container, then do nginx -s reload
Maybe simple, but give it a try.


#11

Are you using self signed certificates on both servers or something like Lets Encrypt. By default NODEJS on only office side wont read machine certificate store so in only office configuration files for NODEJS environment you must add this line NODE_EXTRA_CA_CERTS=./path_to_your_ROOT_CA_Cert.pem so that NODE Will trust your root ca or your Seafile Self signed certificate.

As I recall those configs are in /etc/onlyoffice/documentserver/supervisor/ , and you need this line in every .conf file unde environment variable.


#12

well, my certificates are not self signed. are from a valid ca. Im going to try what yo said about node js. thanks for help.

Im testing all again, over http evrything works as expected, im going to configure https right now again. thanks


#13

actually im having this error

2019-02-06T16:35:10.344] [ERROR] nodeJS - error downloadFile:url=https://telcodrive.telconet.net/seafhttp/files/81196ef9-07cb-4b3a-af3c-0cd51ed73236/dc.doc;attempt=3;code:null;connect:null;(id=be9d7589f94965130bab)
Error: Error response: statusCode:400 ;body:
Bad access token

at Request._callback (/var/www/onlyoffice/documentserver/server/Common/sources/utils.js:250:18)
at Request.self.callback (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request.<anonymous> (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:1161:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage.<anonymous> (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9)