I am experiencing the same issue as shown in the screenshot, but it only happens when trying to open the same file a second time.
Bumping the topic.
Can you say more about your setup?
• Are you running Seafile CE or Pro? Which version?
• Is the server running on standard binaries or Docker?
• What is the host OS?
• What version of OnlyOffice is installed?
• Anything special about the configuration of the server?
Does the problem occur with any document of any kind (doc, docx, xls, xlsx, ppt, pptx)?
Was the document created by OnlyOffice or by another program and uploaded to the server?
The additional information might help the readers point you in a positive direction.
-Thank you
-
Latest CE
-
Standard binaries
-
Ubuntu 22.04
-
Latest
-
Nothing special, running using nginx
-
Only tested on docx
-
Uploaded to the server
I am not able to reproduce the problem.
Is the document previously edited by the same user or a different user?
Is the document open and in use by another user when the error occurs?
It doesn’t matter which user starts the edit, it happens no matter the user.
When you get the error is the document opened by another user or session?
Doesn’t matter
I see this error whenever I edit a file online (in onlyoffice) and it background syncs with my mac using seafile client. The versions get messed up.
If I view the history for the file … the ‘current version’ is still there. But onlyoffice cannot view it.
I fixed this. I figured it was something to do with the ‘key’. After fiddling around with nginx settings I worked out it was nothing to do with seafile. I use Cloudflare for DNS settings and I had ‘cache enabled’ and I guess that was messing with the key. After disabling Cloudflare cache everything works fine (of course I also needed to logout and restart my internet browser to make sure I saw the change)
1 Like