0
Closed for lack of information

OnlyOffice not saving files

lbwtaylor+filerun 5 months ago updated by Vlad R 4 months ago 10

Hello, I am trialing your software. I love FileRun, it's fast and exactly what I need, but I am struggling with OnlyOffice integration, which would be really desirable. 

Both installations are in docker containers on the same server running behind a nginx reverse proxy. SSL on both. I use the JWT token. 


I get the onlyoffice landing screen when I go to its subdomain, saying it's running fine. Filerun->Onlyoffice loads documents and appears to edit them fine, but saving does not result in any change on the server. I looked at the Onlyoffice files and its cache shows it's generating output. The logs aren't showing errors. 

Any suggestions? 


Is there a better way to setup onlyoffice for filerun? 

Much thanks,

Lawrence

is your OnlyOffice available externally via reverse proxy? Did you set a subdomain for it, for example like onlyoffice.yourdomain.com ? 

Under review

Are you getting a confirmation, inside the OO interface, that the changes are saved?
Is the FileRun installation URL (the one you are using to access it) accessible by the OO server, in order to send the data to it?

1) Yes, at the bottom of the site, it says saving document, then all changes saved. 

2) From the server where the OO container lives, yes. I am not sophisticated enough to know if it is accessible from the OO docker container. 

I have noticed some additional behavior. If you re-open the document with OO, it will generate an error message of "The file version has been changed. The page will be reloaded." It also shows in the upper right that another user is editing the document. 

I have also seen one error in the OO log, but it is not reproducible. 


2020/04/24 17:15:29 [error] 380#380: *33 upstream prematurely closed connection while reading response header from upstream, client: 172.24.0.1, server: , request: "POST /5.5.1-76/doc/17030eeca01086846489/c/295/sa1reduj/xhr?t=1587748492229 HTTP/1.1", upstream: "http://127.0.0.1:8000/doc/17030eeca01086846489/c/295/sa1reduj/xhr", host: "office.[*domain*]", referrer: "https://office.[*domain*]/5.5.1-76/web-apps/apps/documenteditor/main/index_loader.html?_dc=5.5.1-76&lang=en&customer=ONLYOFFICE&frameEditorId=placeholder&compact=true"

Finally, Vlad, I very much appreciate your help. I may be out of my depth here. I successfully got the google drive editor working, so I have a fallback for this. 

Best,

Lawrence

it says saving document, then all changes saved.

When a file is being edited by multiple users, the changes are saved on the FileRun side only when all sessions are closed. Even when there is only one user editing, the change is not instant, despite that message and it might take a few seconds. Are you checking the file's modification date, and are you sure that the file is not being touched at all?

So I did a test on this point. I opened a file, made a change, saved it. Then I waited 5 minutes. The I exited, and waited another five minutes to re-open. 

This solved the error pop up re "The file version has been changed..." and seeing another person editing. 

However, still the changes were not saved. File does not show being modified either in the OS or Filerun. 

There was this error:

[2020-04-27T22:13:46.383] [WARN] nodeJS - Plugins watch exception (https://nodejs.org/docs/latest/api/fs.html#fs_availability).
[2020-04-27T22:13:46.413] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode
[2020-04-27T22:30:27.228] [WARN] nodeJS - UpdateVersion expired: docId = 8432bdb4383897521998

I am afraid I am out of suggestions. If you contact us at tech-support@filerun.com with the URL of your FileRun installation and a test login, we can troubleshoot the problem for you.

I rebuilt my server from scratch as part of a separate project, and this problem was resolved. I am not aware of actually changing anything that would provide any insight on the error for future users :/

Thank you for your help troubleshooting.

Sorry that last comment is anonymous, I was not logged in, but it was from me. 

Closed for lack of information