Collabora Online Problems & Issues
Real user-reported problems, complaints, and limitations for Collabora Online. Based on analysis of 14 signals.
Overall score: 60/100
Issues by Category
'Unauthorized WOPI host' error when opening documents
Dozens of threads report this after installs, migrations and Docker or TrueNAS setups. Causes are a container started with the wrong URL or a WOPI allow list in Nextcloud that does not include the address Collabora calls from; Cloudflare and reverse proxies make the right IP hard to find.
'Could not establish connection to the Collabora Online server'
Shown in Nextcloud's Office settings when Nextcloud cannot reach Collabora. Reported on Nextcloud, Cloudron and Plesk forums; fixes range from firewall and Docker start order to internal DNS and adding the richdocumentscode proxy location to nginx.
Built-in CODE server not working in Nextcloud
The one-click 'Collabora Online - Built-in CODE Server' app is the easy path, but users report connection failures, a wrong ARM64 vs x86 package, a proxy.php 400 bug in one release and constant reconnect attempts that slow Nextcloud.
Reverse proxy: 'socket connection could not be established'
Collabora depends on WebSockets. Behind nginx, Apache, Traefik or Plesk, missing Upgrade headers, a subpath, short timeouts or double SSL termination produce socket errors or documents that open and then disconnect.
Collabora 'Document loading failed' in Nextcloud
The most common thread on the Nextcloud and Collabora forums: the editor spins and then shows 'Document loading failed' or 'Failed to load Nextcloud Office', often while the admin page still says the server is reachable. The Collabora log usually shows WOPI::CheckFileInfo failing because Collabora cannot reach Nextcloud back.
Collabora document cannot be saved or edits are lost
Users report 'document cannot be saved' errors, edits not persisting and large Word files failing to save. Causes traced in threads include Docker MTU and hairpin NAT problems, WOPI errors and a missing Nextcloud user key.
Documents open read-only or switch to read-only
Reports of documents that open read-only in the browser, flip to read-only after a few minutes, are greyed out on Android, or are locked while open in a desktop app via 'Edit locally'. Share-link permissions are another cause.
Why is Collabora so hard to set up?
Self-hosters describe a chain of failure points: two servers that must reach each other over HTTPS, matching protocols, WebSocket proxying, certificates, DNS inside containers and the WOPI allow list. The official troubleshooting page is a connectivity checklist rather than a guided fix.
Why is Collabora Online so slow?
Complaints about slow loading and laggy typing over high-latency connections, slow large or image-heavy files, and VMs with generic CPU types forcing slow fallbacks. A Nextcloud 34 thread reports the built-in server freezing or showing black boxes after the upgrade.
DOCX formatting looks different from Microsoft Word
Collabora is built on LibreOffice and its native format is ODF. CERN's service page warns DOCX may partially lose formatting and recommends ONLYOFFICE for Microsoft formats; the Collabora forum has threads on DOCX rendering differences, and release notes keep listing DOCX round-trip fixes.
Collabora missing fonts, custom fonts not showing
Documents render with substitute fonts, and fonts uploaded through Nextcloud's Office settings sometimes never appear in the font list until Collabora and Nextcloud are restarted; some users report they never appear at all.
Collabora Office mobile apps feel unfinished
The iOS app was called unstable and unpolished by a 2021 reviewer, and App Store reviews mention it getting stuck. The Android app rates better (around 4 stars on Google Play) but users still report read-only and greyed-out buttons.
Doesn't work with Nextcloud server-side encryption
Both the Nextcloud admin manual and the Collabora-for-Nextcloud docs list encryption as unsupported, a blocker for admins who enabled Nextcloud's encryption module.
Free CODE edition is 'for home use', not 100 users
The official docs say the Docker image is meant for home use and won't handle around 100 users, pointing to a paid subscription. Older CODE builds showed a 10-document / 20-connection warning; forum replies disagree on whether any cap remains.
Regret Patterns
Common reasons users regret choosing Collabora Online.
The 'one-click' built-in server didn't work
Users enable the built-in CODE server expecting instant editing and end up debugging DNS, proxy and allow-list settings.
It worked until an upgrade
Nextcloud or Collabora updates break a working setup with loading failures or slowness.
Word files came back looking different
Teams sharing DOCX with outside partners find layouts shifting after round-trips.
Remote users find it laggy
Typing and loading are slow over high-latency connections compared with local editing.
Encryption had to be turned off
Admins discover Collabora does not support Nextcloud's server-side encryption.
Outgrew the free edition
Teams that started on CODE find the home-use edition is not meant for dozens of users and need a subscription.
When Collabora Online Breaks Down
Specific scenarios where Collabora Online fails or underperforms.
Behind Cloudflare or a reverse proxy
WOPI allow lists and WebSocket forwarding fail, giving Unauthorized WOPI host or socket errors.
Docker container started with the wrong URL
Using the Collabora host instead of the Nextcloud URL produces 'No acceptable WOPI hosts found'.
Nextcloud can't resolve its own hostname
The built-in CODE server cannot connect when the server cannot reach itself by its public name.
Proxmox VM with generic CPU type
Missing modern instruction sets forces slow fallbacks and long load times.
Office app restricted to some groups
Restricting the Nextcloud Office app to groups triggers 'unexpected connection error'.
Large image-heavy documents or complex spreadsheets
Loading slows sharply; recent release notes list fixes for exactly these cases.
Docker network MTU mismatch
Saves fail and later opens return WOPI errors until the Docker MTU matches the host.