Nextcloud · Help

Nextcloud Office: Collabora reports Document loading failed?

Office connection appears healthy but documents will not load? Check browser access and both server-to-server connection directions.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

Document loading failed after a successful Nextcloud Office check can involve a connection path that check did not exercise. A document requires browser access to both services, Nextcloud reaching Collabora and Collabora reaching Nextcloud. First trace one small test file by timestamp across those paths. Compare actual hosts, responses and logs from each runtime environment; successful discovery alone does not establish successful document saving.

Source basis: Q1 · Q2

Applies to
The original report concerns Nextcloud 35 and Collabora CODE behind Traefik. Observed WOPI redirects do not establish a universal cause; versions and actual proxy paths matter.
How to verify the result
The same harmless test document opens, saves a small edit and shows it after reopening, with certificate verification and the intended access controls still enabled.
Your first check

Which required connection fails during a real document-opening attempt?

Nextcloud reports that the Office integration is reachable, yet opening a file produces Document loading failed or a socket error. A successful connection check does not necessarily cover every route required to open and save a real document.

Separate the connection paths

An original report concerns Nextcloud 35 with Collabora CODE behind Traefik. It includes redirects associated with WOPI requests, but does not establish a universal cause. Q1 Nextcloud explicitly lists browser access to both services and connectivity between Nextcloud and Collabora in both directions. Q2

Checking whether your own browser opens the Office landing page is therefore insufficient. The two servers may see different DNS answers, routing or certificate trust.

Trace one small document end to end

  1. Define a narrow test. Use a small non-confidential document and record opening time, user, format and exact error. Determine whether every file fails, only one format fails or a single document is affected.
  2. Inspect the browser route. Access the discovery and capabilities endpoints intended for your Office hostname, then observe failed browser requests during document opening. Record status codes and unexpected destination hosts without sharing session tokens.
  3. Test Nextcloud to Collabora. Have the administrator check those endpoints from the Nextcloud container or its actual runtime environment. A successful host-side request can overlook a different container route.
  4. Test Collabora to Nextcloud. From that environment, inspect the intended Nextcloud address and correlate Office and Nextcloud logs. A redirect to another host, protocol change or certificate discrepancy is evidence to explain, not a reason to apply an arbitrary workaround.
  5. Relate WOPI and proxy settings. If Collabora reports an unacceptable WOPI host, compare the allowed Nextcloud domain with the hostname actually used. For socket failures, investigate the particular proxy route in its logs. Do not broaden a host allowlist to every possible destination.

Apply and validate the identified correction

Correct the demonstrated hostname, protocol, proxy-route or trust problem. Keep certificate checking and access controls enabled. Afterwards, the same test document must open, accept a small edit, save and show the new content when reopened. Successfully retrieving discovery data alone does not establish that complete result.

Keep a compact record of each tested direction and its response. It helps the server operator address the failing route without changing unrelated paths that already work.

Frequently asked questions

Does a green Nextcloud check prove Collabora is fully reachable?

It confirms the path that check tested. Browser access and the return connection may still fail separately.

What belongs in a support request?

Provide Nextcloud, Office app, CODE and proxy versions, a small connection diagram, test timestamp and corresponding log lines from both services. WOPI URLs can contain secret tokens and must be redacted before sharing.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0208 with KAN KAI WORKS.

Support with this issue

We investigate Nextcloud using your error message, versions and a narrowly scoped example.

Describe your case →Related service: Data & improvements

Sources

Sources checked on 5 November 2026. Individual reports do not establish general prevalence.