OnlyOffice timing out when used with Nextcloud documents
-
Since the update rolled out last night, on two Cloudron servers I maintain which use Nextcloud and OnlyOffice, we can now no longer open documents in OnlyOffice.
The usual splash screen appears, the loading animation begins, but no percentage shows, and it eventually times out with an error dialog saying: "Connection to the server has been interrupted"
Inspecting the browser console, I see that the websocket connection is repeatedly attempted, until eventually it fails. This is in Firefox on Linux for me, but it has been reported by users on other OSes (Windows I think) and presumably other browsers.
There appears to be no errors I can see in the OnlyOffice app server logs, or the NextCloud logs. the OnlyOffice web page indicates no problems. I've restarted the apps and the server. It still doesn't work. But as I said, the thing which makes me think it may be a problem with the update is that it is behaving like this on two Cloudron instances, running on different servers for different organisations I'm involved with.
Is there anything else I can try to work out what the problem is?
Thanks
-
Since the update rolled out last night, on two Cloudron servers I maintain which use Nextcloud and OnlyOffice, we can now no longer open documents in OnlyOffice.
The usual splash screen appears, the loading animation begins, but no percentage shows, and it eventually times out with an error dialog saying: "Connection to the server has been interrupted"
Inspecting the browser console, I see that the websocket connection is repeatedly attempted, until eventually it fails. This is in Firefox on Linux for me, but it has been reported by users on other OSes (Windows I think) and presumably other browsers.
There appears to be no errors I can see in the OnlyOffice app server logs, or the NextCloud logs. the OnlyOffice web page indicates no problems. I've restarted the apps and the server. It still doesn't work. But as I said, the thing which makes me think it may be a problem with the update is that it is behaving like this on two Cloudron instances, running on different servers for different organisations I'm involved with.
Is there anything else I can try to work out what the problem is?
Thanks
@wu-lee yes, the package was already revoked since it's broken. Please revert to the previous package version.
-
Ok, it's described here: https://docs.cloudron.io/backups/#restore-app
-
@wu-lee yes, the package was already revoked since it's broken. Please revert to the previous package version.
@girish said in OnlyOffice timing out when used with Nextcloud documents:
@wu-lee yes, the package was already revoked since it's broken. Please revert to the previous package version.
I have the same issue.
I checked the version of OnlyOffice that I have now, it is v1.14.0 while the previous version was v1.10.1I am going to restore the v1.10.1 and hope everything goes well.
-
The 1.14.0 package was already revoked a while ago because of this issue. I think somehow your server got the update in the small time frame it was available.
-
The 1.14.0 package was already revoked a while ago because of this issue. I think somehow your server got the update in the small time frame it was available.
-
@girish Do I need to do anything now, I have switched off the automatic updates.
Please let me know If I can update when the next version comes out.
Thanks Girish!@jagan you don't need to turn off automatic updates. Since the package is revoked, your installation won't update to that one anymore.
-
I reinstalled, but now the token isn't valid anymore and I'm not shure where to find the new one:
-
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
