-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes made to documents created in Onlyoffice are not saved correctly in Nextcloud #369
Comments
Our situation: About 5 people spent many hours during about one week on editing on many documents for an upcoming private film festival. The fesitval has no big funding and people have to work from home due to the current situation with Corona. That's one of the reasons to use Nextcloud and the community edition of OnlyOffice. Now nearly all changes are only visible when opening the documents in OnlyOffice in the browser, but the changes did not get saved in the actual files! Nextcloud itself still thinks, the files are older than 5-7 days and when downloading the files, all changes are missing! We discovered this by accident since I wondered, why people told us they already finished their work and the changes are not visible in the downloaded files. Somehow all the edits still are somewhere within the documentserver but never got written back to the actual files. I use Nextcloud 19.0.3 and OnlyOffice 5.6.4 in a Docker container and did not have any issue 12 months ago when we first tried this with older versions. But some of the last updates seemed to have introduced some very serious bugs. The editor always "All changes saved" in the status bar but actually nothing was saved to the files at all. Right now two people working on the tedious job to get all the content out of more than 50 documents with copy & paste out of the browser into a local editor running on the PC and we still don't know if all all changes are save then or not - and the deadline is in 4 days! (updated due to the super quick response by the OnlyOffice team) |
Could you please install the latest version of the connector and let us know if the issue still can be reproduced. |
1 ONLYOFFICE has nothing to do with Community Documentserver. https://github.com/nextcloud/documentserver_community 2 Our product is available in our official repository only and has the name ONLYOFFICE Document Server. 3 Please contact the author of the mentioned by you piece of code - the Nextcloud team who just took the AGPL v3 core of our software to add document editing to their platform not in the regular, well-tested and supported by our team way - via an integration app by ONLYOFFICE - but built-in directly generating a lot of troubles. Only Nextcloud can help with it now I'm afraid. Sorry, but we are not ready to support the Community Documentserver as we see a lot of issues with it as well and never recommend it. Please use our official open source software ONLYOFFICE, not the imitation created by other companies. |
To clarify the situation: First of all: I am already in contact with OnlyOffice support - thanks for your active support! About my setup: I use the Docker container, not the Community Documentserver. And I have never used the Community Documentserver ever. The issues started somewhere in the last couple of weeks - I'm not sure if it was after updating Docker to onlyoffice/documentserver 5.6.4 or even earlier. At the time I noticed the issue I used the Docker version 5.6.4 and the Nextcloud integration app 6.0.0, however editing was done with an earlier version of the app as well, I just can't remember which version that was exactly. The first thing which happend is that people told me that they get a message during editing sessions with spreadsheets that the document was changed and has to be reloaded. Sometimes this happend right after opening a document, sometimes during the editing session. In Chrome this happend less often as in Firefox. This did not happen with documents, but for documents the changes did not get synced back to the file in Nextcloud but only stayed inside Docker - so you could open the document and see the changes inside the OnlyOffice editor but not in the file when downloading it. I meanwhile updated the Docker container to the latest version which seems to be 5.6.5 and also activated the new option "Keep intermediate versions when editing" in the Nextcloud integration app as suggested in your article: Some quick tests look promising - so far I could not reproduce the problems again. However I will do more thorough testing and let you know what the result is. |
I had the same problem, if "keep intermediate versions" could solve the problem at least for now it would be an easy fix - if this could be set as default As long as it "works" as now it should be discourage to be used in production |
Just an update: In spreadsheets I still have this error with "Internet connection has been restored" which comes very often about 1-2 minutes after the spreadsheet gets edited: After this message no further editing is possible, but at least the changes don't get lost. I have another setup which runs the Docker version 5.6.0 and not 5.6.4 - and there this problem does not happen. I will try to downgrade the machine and see, if this changes anything. |
Ok, no change - even with 5.6.0 the error appears on that machine. So somehow the reliabiliy of the Docker version is affected by the environment it runs in. The environment which seem to be OK with 5.6.0: Debian Linux 10 on a dedicated machine I was courious: would the dedicated Debian server also work fine with the Nextcloud installation on the Ubuntu VM? So I configured the Nextcloud integration app on the Ubuntu VM to use the Onlyoffice Docker version on the dedicated server. And the result: yes, it seems the version on the dedicated server just runs fine, also with the Nextcoud integration app on the VM. However - using the dedicated server is not an option for me - the servers belong to different user groups and must not be mixed. Update 1: I just rebooted the Ubuntu machine just to see if this changes anything - but no, no change. Still the same connection error. However - everything else on that machine just runs fine (Apache webserver, MariaDB; Dovecot, Postfix etc.) and I never had any issue with any other service there yet. Update 2: I now completely removed docker and reinstalled it according to https://docs.docker.com/engine/install/ubuntu/ No change - still getting the connection error in the OnlyOffice spreadsheet editor :-( Update 3: As a last resort I tried downgrading from Docker 19.03 to Docker 18.06. No change - still getting the connection error in the OnlyOffice spreadsheet editor :-( And just to be sure I also downgraded OnlyOffice to version 5.5 - but no change there as well. So it seems the OnlyOffice Docker version can't be used on some servers. |
I did another test: not using Docker any more but installing the Onlyoffice Documentserver as described in https://helpcenter.onlyoffice.com/de/server/linux/document/linux-installation.aspx But again: but no change there as well. What is this? Why does the document server always loses the connection? No other service on this machine ever had any issue at all. So it must be some weird problem inside the OnlyOffice Document server. |
This is the log about the incident in
|
Downside - the undo function is not available any more !! |
Another Update: Meanwhile I've set up the OnlyOffice Documentserver on another complete new virtual server - 2 cores, 8 GB RAM, 160 GB storage. Besides OnlyOffice and Apache with Let's Encrypt as a proxy nothing else was installed. But again the same pesky error in spreadsheets as soon as I start editing :-(. Since there is one server one which is it seems to work (also using Apache as proxy), I can only assume there is some requirement which is only met by this single server. Any suggestion is welcome. |
My problem is solved for me. It was caused by a misconfiguration of the Apache proxy (which had a ProxyTimeout setting - set once a long time ago to solve another issue and just forgout that :-( Mea culpa maxima). Sorry for the fuss - but the Docker version works fine so far, you just have to confgure it correctly. |
@arnowelzel , please could you post your correct apache config - or at least the crucial line which fixed your issue |
My problem is still open. I will check it out tonight. |
First of all: the problems you described have nothing to do with ONLYOFFICE itself! You have to ask the team of Nextcloud to look into their implementation of the "Community Documentserver"! See here: https://github.com/nextcloud/documentserver_community I don't use this app and never did. I only use the official Docker container which you can find here: https://hub.docker.com/r/onlyoffice/documentserver/ along with the official integration app: https://apps.nextcloud.com/apps/onlyoffice. The Docker container was set up with these commands on my Linux server:
For Furthermore the relevant options in Apache to make the document server available via HTTPS (this serves then as the endpoint for the Nextcloud integration app):
My mistake was the option But again: this is for the Docker version 5.6.5 and not the "Community Documentserver"! |
Thanks |
@CB-IT-Chris @ferdiga If you are using our official method of integration (Nextcloud + dedicated Document Server instance as per our installation guide), we will be glad to answer your questions. Please see more info on our forum. |
@arnowelzel As I see your issue is not similar to the first message. |
problem:
Changes made to documents created in Onlyoffice are not saved correctly in Nextcloud. Synchronizing from Nextcloud Client to Onlyoffice will overwrite any changes made in Onlyoffice in a file. (data loss)
Adjustable:
Login in the Nextcloud and via the browser (Onlyoffice) create a new document, enter data and save it
Now open the just created document via the local PC and you can see that there is no content available.
If you now save or synchronize the document, everything in this document that was created in Onlyoffice will be overwritten.
Environment:
Nextcloud: 19.0.2
Community Document Server: 0.1.7
ONLYOFFICE: 5.0.0
The text was updated successfully, but these errors were encountered: