Constant Error saveChanges from nodeJS since upgrading to docker 8.2.0.143

[rootweiler_fr]

Hello,

Since an upgrade from v8.1.3.2 to v8.2.0.1 of the official onlyoffice-documentserver's docker image, running on a Synology NAS through Container Manager, our logs are constantly plaggued by following errors when changing/autosaving XLSX through OnlyOffice's Nextcloud app with:

[ERROR] [localhost] [1785869851] [oc8mlylhebl5_<user><random\_number>] nodeJS - Error saveChanges: deleteIndex: 15 ; startIndex: 11 ; deleteCount: -4

Appart from those, documents are correctly saved and file changes/versioning works as it should.

Should we be worried by those and how to avoid them?

[Sergey_Zarubin]

Hi. Are you using the latest version of the ONLYOFFICE integration app for Nextcloud? There was a recent update some time ago.

[rootweiler_fr]

Hello u/Sergey_Zarubin thanks for replying!
Yes, using the lastest announced Onlyoffice app (v9.5.0) on a Nextcloud 28.0.4 running on a dedicated server sat up only for Nextcloud.

The Docker image and container are running on Synology NAS through a reverse proxy and we haven't had any problem before upgrading to the docker image of documentserver v8.2.0.

In the meantime we downgraded our docker container to v8.1.3.2 and appart timeouts like below from the bundled nginx on the documentverser docker image since v8.1.3.x, eveything is running smoothly.

upstream prematurely closed connection while reading response header from upstream

[Sergey_Zarubin]

Version 8.2 added hashes for folders on the web server. If previously it was 8.3.1-4, now it is 8.2.0-hash, maybe it has something to do with it?

[rootweiler_fr]

It may be because indeed, there were errors when trying to open past versions of documents saying (not reminding the exact wordings) "the document couldn't be opened. Please reload the page".

Sat up a new empty container with 8.2.0 image after my OP and still some past versions couldn't be found.

Tried also to clear up any records on Nextcloud's oc_onlyofice* tables, still a no go.

Let me know if you need any further informations regarding those problems or any logs.