Every day at a random time the connection to OnlyOffice in NextCloud is disconnected

[Kepmas1er]

This issue is unique.

• [X] I have used the search tool and did not find an issue describing my bug.

Operating System of DocumentServer

Docker

Version information

7.2 OnlyOffice Community Edition

Expected Behavior

Stable operation without disconnection

Actual Behavior

Every day you have to manually click on the “save” button in NextCloud to restore the connection with onlyoffice

Reproduction Steps

No response

Additional information

No response

[Kepmas1er]

Help me pls fix bug, or suggest a script to detect disconnections and reconnect

[igwyd]

Hello @Kepmas1er, we know about this and already fix it, issue https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/882, please update onlyoffice-documentserver to the actual version - 7.5.1 now and update the onlyoffice-nexcloud connector.

[tromlet]

I mean, I'm on 7.9.4 on Nextcloud 25.0.13 and I still seem to have this issue.

[igwyd]

Did you read the recommendations from this, did it help?

[ihdem]

From several weeks, some of my customer have the same issue. After some research, today i have found a solution. In the config.php file of your nextcloud installation, add or modify this line 'overwrite.cli.url' => 'https://fdqn-of-your-nextcloud-instance'! After try this comment sudo -u www-data php occ onlyoffice:documentserver --check. If no error, that's done !

[quentinDupont]

If I understand well this thread, set this parameter :

sudo -u www-data php occ config:system:set onlyoffice editors_check_interval --value=0

(And not sudo -u www-data php occ config:app:set onlyoffice editors_check_interval --value=0 apparently)

And we have to wait that this PR (code modification) is merged for future release : https://github.com/ONLYOFFICE/onlyoffice-nextcloud/pull/965 At the moment, it's merged in "develop" branch, not master and I don't know their flow. Last version of Onlyoffice app was in december, so hopefully, we will get a new version soon.

[rasos]

We have a similar behaviour when the external OnlyOffice server goes offline (e.g. for maintenance), then the nextcloud app discontinues the connection and does not check again later if the OnlyOffice server is again available. Workaround is that we have to re-confgure the OO server settings at every nextcloud instance.

We have now set the editors_check_interval to 0 as recommended here (and overwrite_cli was always set). However, it would be better if the app does the check regularly and reconnects if the OnlyOffice server is again available.

[tromlet]

We've actually more or less resolved this error on our end - your Nextcloud servers and their corresponding OnlyOffice instances REALLY need to be in pretty damn close time sync. Like, no more than two to three seconds apart. You probably don't need a hosted NTP server on your network (though it wouldn't hurt - and you may have one already), but you do need both servers to check time pretty frequently and arguably from the same source. Once we configured our internal NTP servers and got Nextcloud and OnlyOffice pointed at them, they were overwhelmingly more reliable.

Nextcloud DOES seem to give up trying to find the OnlyOffice servers after a certain period of time (a bit frustrating) but we've also had issues where the OnlyOffice service messes up and doesn't work, even when both servers are up and in sync. It's rare, though, and we haven't experienced it since implementing a daily cron job that restarts all of the OnlyOffice ds-______ services.