Connect Nextcloud and Collabora Online
Connect Nextcloud and Collabora with a defined WOPI trust boundary, production licence, proxy checks and document fidelity acceptance criteria.
Last updated
In short
- The browser and both servers need the correct network paths.
- Restrict WOPI requests in both Nextcloud and Collabora.
- Evaluate real documents before treating browser editing as feature parity.
On this page (6)
Integrations · Part of Sovereign workplace
Separate file storage from document editing
Nextcloud stores and shares files; Collabora Online provides the browser editing service. Connecting them creates a three-party interaction involving the user’s browser, Nextcloud and Collabora. A server-to-server health check can pass while the browser still cannot open the editor, so each path needs its own validation.
This is a reference integration and acceptance procedure, not a tested production configuration. Start with a supported Nextcloud server and Office-app combination, a selected Collabora release and the production licence appropriate for the intended users. Collabora’s FAQ distinguishes its development edition from the supported production offering. A development image is useful for evaluation but should not silently become the production support plan.
Draw the network paths before changing settings
| Path | Purpose | Acceptance check |
|---|---|---|
| Browser to Nextcloud | Authentication, file selection and sharing | Valid HTTPS and expected external hostname |
| Browser to Collabora | Editor interface and live collaboration | Editor loads and maintains its connection |
| Nextcloud to Collabora | Discovery and service interaction | Correct editor endpoint and trusted certificate |
| Collabora to Nextcloud | Authorized file access through WOPI | Expected host permitted; unrelated host denied |
| Administrator to each service | Configuration and diagnostics | Separate restricted administrative access |
Use stable external hostnames, such as a file-service name and a separate office-service name. DNS must resolve correctly from the browser and the containers or hosts running the services. If a reverse proxy terminates TLS, document which internal hop is encrypted and how the service learns its public URL.
Do not fix certificate or hostname errors by broadly disabling verification. The Nextcloud troubleshooting guide is a useful starting point for discovery, connectivity and WOPI-host errors. Capture sanitized error messages and the failing direction of traffic before changing access rules.
Configure trust narrowly
Set the Collabora server URL in the Nextcloud Office administration settings. The configuration manual also documents group restrictions and WOPI controls. Restrict Nextcloud’s WOPI request allowlist to the expected Collabora origin addresses and restrict Collabora’s accepted WOPI hosts to the intended Nextcloud service.
The correct addresses depend on your proxy and network topology. An allowlist containing the entire Internet is not an acceptable substitute for understanding which address Nextcloud actually sees. When autoscaling or failover changes those addresses, update the design deliberately rather than adding increasingly broad ranges.
Treat document-access tokens as credentials. Avoid logging complete WOPI URLs if they contain tokens, and limit access to diagnostic traces. Access to the editor is not permission to every file: verify that Nextcloud’s sharing and file-access decisions remain authoritative.
Use a document fidelity matrix
Choose a representative set of synthetic or approved documents. Include material created by the actual office applications your staff use, because a simple text document does not reveal spreadsheet or layout limitations.
| Document feature | Test action | Acceptance owner |
|---|---|---|
| Fonts and page layout | Compare exported PDF and printed pagination | Document owner |
| Tracked changes and comments | Add, accept, reject and reopen changes | Review team |
| Spreadsheet formulas | Compare known inputs and expected outputs | Spreadsheet owner |
| Charts and embedded objects | Edit and reopen in both environments | Business workflow owner |
| Templates and protected areas | Create a new document and attempt restricted edits | Template maintainer |
| Macros or external integrations | Identify whether the workflow is supported at all | Application owner |
Installed fonts matter to layout. Record the font packages and their licensing alongside the editor version. A document that opens can still have an unacceptable visual or computational difference. Mark unsupported features as retained workflows or explicit redesign work; do not convert them into an assumed success rate.
Exercise collaboration and access changes
Have two synthetic employees edit the same document, then interrupt one browser connection and reconnect it. Check saved content, version history and conflict behavior. Repeat with a read-only collaborator and a guest link. The read-only identity must not gain edit rights through the editor or a direct file request.
Remove a share while the document is open. Observe when the editor stops accepting changes and whether any later save reaches Nextcloud. This establishes the actual revocation behavior for your versions. Test a renamed or moved file, a large spreadsheet and a user whose quota has been reached.
An editor outage should produce a clear error without claiming that unsaved work was persisted. Document the user action needed to recover the session. The fallback might be downloading a file into an approved desktop workflow, but only where the file’s access policy permits it.
Back up the right state and control upgrades
Nextcloud recovery requires its database, file storage, configuration and relevant application state. Collabora also needs its configuration, certificates, fonts and licence information preserved. Coordinate these records so a restored file service can still trust the intended editor.
Before changing versions, record the supported pairing and run the document matrix in a separate environment. Keep prior configuration and matching backups. If you revert after users have edited documents, preserve and reconcile those edits; replacing storage with an older snapshot can lose valid work.
The integration is ready when all network paths are understood, unauthorized WOPI access is denied, representative documents are accepted and a restore reestablishes editing. Those are the useful boundaries for scoping a workplace pilot.
Sources and further reading
Use the linked documentation to confirm the version, edition and contract that apply to your project.
