Update Nextcloud and OnlyOffice Without Breaking the Integration
Most broken integrations were fine yesterday - and then somebody updated something. The order and the secret decide whether yours survives.
By Technical AnshuLinux ServerSelf HostedMaintenance
Watch the full video - Nextcloud and OnlyOffice setup and integration, step by step
Nothing about updating this pair is hard - except the two ways it silently goes wrong: a live editing session caught in a restart, and a JWT secret that quietly changes under the connector. This page gives the safe order and the short acceptance test that proves the integration survived.
Update order that keeps the pairing alive
Step 0Full backup taken
Step 1Update Nextcloud
Step 2Update connector app
Step 3Update OnlyOffice Docs
Step 4Re-test one real document
Skipping step 0 is how a routine update becomes a recovery project.
Example safe order - backup first, the editor last, a real test at the end
1
Rule Zero - Backup, Then Announce a Quiet Window
Updates of this pair go wrong in a specific way: not during the update, but in an editing session that was live while services restarted. Schedule a quiet window, tell the team to close documents, and take the full backup first - data folder, database dump, config, and the integration settings including the JWT secret, exactly as the backup guide describes. If anything below goes sideways, that backup is the whole recovery plan.
2
Update Nextcloud First, One Version Step at a Time
Nextcloud must be updated stepwise through each major version - it does not support skipping majors. Read the admin overview warnings before and after.
Use the built-in updater or your package/Docker route consistently; mixing methods between updates is how installs corrupt.
After the core update, update the apps - the ONLYOFFICE connector app included. A new Nextcloud with an old connector is a common cause of a suddenly broken editor.
Run the post-update housekeeping the admin panel asks for (missing indexes and similar occ tasks) instead of leaving warnings to pile up.
3
Update OnlyOffice Docs Second
For the Docker route, updating means pulling the new image and recreating the container with the same environment values - above all the same JWT_SECRET and JWT_ENABLED settings. Change the secret during an update and you have silently un-paired the servers; the documents will fail with token errors until the connector is updated to match.
For package installs, update through the system package manager and restart the Docs services. Then check the healthcheck address answers true before letting anyone edit.
4
The Five-Minute Acceptance Test
Open an existing document - it must load and show your content.
Type a line, close, reopen - the line must be saved in the real file.
Open it from a second account at the same time - co-editing cursors must appear.
Create one new document from the New menu - the connector's create path must work too.
Only announce "done" after all four pass. And a rhythm worth adopting: small updates every month or two are calm; the heroic annual leap across many versions is where the breaking changes live.
Watch the Complete Video Guide
Build the system with the video, back it up with the backup guide, and keep it alive with this update routine.
You can, but the safer habit is Nextcloud first, its apps (including the connector) second, and the Docs server last, because the connector is the piece written against both sides. Whatever order you choose, the secret must stay identical and the acceptance test decides when you are done.
The editor broke right after an update. What do I check first?
Two things: the connector app version against the new Nextcloud (update the app), and whether the Docs container was recreated with the same JWT secret. Those two account for most post-update breakage - before any reinstall is even considered.
How often should I update?
Little and often wins. A monthly rhythm keeps each step small and reversible; skipping a year stacks many major versions, and Nextcloud in particular must climb them one at a time. Security updates on a public server should never wait for the monthly window.
This guide is based on the Technical Anshu video on Nextcloud and OnlyOffice integration. Stuck on a step? Ask in the video comments - you will get an answer there.