Clear Nextcloud’s File Locking Warning with Redis
Enable reliable Nextcloud file locking, choose the right Redis or Valkey backend, and verify the warning clears without risking concurrent file changes.
When a WOPI host reports “proof validation failed” or “Invalid WOPI proof,” first confirm which system logged the rejection. If the storage host is rejecting Collabora’s signed request, check the proof-key pair and the discovery response before changing WOPI host allowlists or disabling proof checks. For package installs, Collabora normally generates the key pair; for Docker, Kubernetes, and multi-replica deployments, the pair must be supplied and persisted consistently.
WOPI proof validation uses a signed request and the public key advertised by the WOPI client in its discovery metadata. It is separate from Collabora’s list of trusted WOPI hosts, TLS certificate validation, and the storage host’s access-token check. A key regeneration can help when the private key is missing or does not match the advertised public key, but it can create a new mismatch if only one replica changes or a host still has cached discovery data.

| Evidence in the log | Likely area to check |
|---|---|
| Storage host says “Invalid WOPI proof” while receiving CheckFileInfo or another WOPI request | Collabora’s proof key, the host’s discovery data, URL reconstruction, or timestamp |
| Collabora says “Unauthorized WOPI host” or “No acceptable WOPI hosts” | The WOPI host allowlist / domain configuration, not the proof key |
| Token invalid, expired, or access denied without a proof error | Host-issued access token, permissions, or token expiry |
Check one failed request in both Collabora and storage-host logs; a browser spinner alone does not identify a proof-key failure.
Start with the least disruptive option. On a package-based installation, verify the existing key files and service logs first; current Collabora documentation says RPM and Debian package installs generate a WOPI proof key pair automatically. If those files are present and stable, rotating them is usually unnecessary.

| Deployment | Recommended action | Trade-off |
|---|---|---|
| Single package-managed server | Keep the generated key pair; repair permissions or regenerate only if missing or mismatched | Minimal change, but verify your package version and configured paths |
| Single Docker container | Generate a pair once and mount it persistently into the container | Requires a persistent volume and correct read access for coolwsd |
| Kubernetes or multiple replicas | Mount one shared Secret/key pair in every Collabora instance | Consistent signatures across replicas; rotation must update the host’s discovery view too |
| Host URL changed behind a proxy | Verify public scheme, host, path, and query string used for signature validation | More involved than rotating keys, but avoids unnecessary credential changes |
Collabora’s 24.04 manual says the public Docker image does not include a proof-key pair; generate one and mount it persistently. The official Helm chart supports proof-key Secrets. Never generate a separate pair for each replica, or load balancing can make failures intermittent.
coolwsd.xml settings for the proof-key path and check whether both the private key and public key are available. Common locations are under /etc/coolwsd/, but package and container layouts can differ. Never paste the private key into logs, tickets, or chat.sudo openssl pkey -in /etc/coolwsd/proof_key -pubout -outform DER | sha256sum and openssl pkey -pubin -in /etc/coolwsd/proof_key.pub -outform DER | sha256sum. The resulting hashes should match. If your paths differ, substitute the actual configured paths. If the private key cannot be read, correct its ownership and permissions according to the service’s security model; do not make it world-readable.sudo coolconfig generate-proof-key where that utility is installed. For Docker, generate the pair in an appropriate persistent location, then mount both files where Collabora expects them and ensure the coolwsd process can read the private key. On a managed platform, use its supported Secret mechanism instead of hand-editing a running pod.
Check time synchronization on both systems. WOPI proof requests include a timestamp; a host can reject an old or out-of-window timestamp. Confirm that NTP or the platform’s time service is healthy and that the servers report sensible UTC times. Do not loosen timestamp checks to work around a clock problem.
Next, inspect the public URL the host uses to reconstruct the signed request. The proof is tied to the request URL, including relevant query parameters, and the WOPI specification requires the URL representation used for validation to match the signed form. A reverse proxy that terminates HTTPS can make the application see an internal HTTP URL even though Collabora signed the public HTTPS URL. Configure trusted proxy headers and the application’s external URL settings according to the WOPI host’s official guidance; do not rewrite proof logic or strip query parameters.
If the proof fails only after a key rotation, refresh discovery and verify all Collabora replicas expose the same public key. If only requests routed through one proxy or one replica fail, compare that path’s logs and configuration rather than rotating the key again. Disabling proof validation can weaken a security check and should not be used as a production fix.

A successful document open verifies that path only; repeat the check for each WOPI host and proxy route you operate.
Enable reliable Nextcloud file locking, choose the right Redis or Valkey backend, and verify the warning clears without risking concurrent file changes.
Fix common Nextcloud scan findings with current updates, HTTPS and HSTS, precise reverse-proxy trust, and checks against the public server.
Back up Nextcloud’s files and MariaDB together, schedule encrypted Restic snapshots with cron, and verify recovery without risking the live server.
Configure Nextcloud SSE for the storage that needs it, protect encryption keys, and measure transfer and CPU impact before encrypting existing files.
Connect Nextcloud’s file search to Elasticsearch, index document contents, and choose a setup that fits your server and security needs.
Configure Nextcloud to remove deleted files after a defined retention period, schedule background jobs reliably, and avoid commands that purge every user’s trash.
Run Nextcloud’s OCC repair safely, preview the database changes, and check why the warning might remain.
Allow larger Nextcloud browser uploads by aligning PHP, Nginx or Apache, temporary storage, and timeout settings—and verify which limit is blocking the file.
Set the PHP memory limit Nextcloud actually uses, restart the right service, and confirm the 512 MB setting in Admin Overview.
Mount a compatible object-storage bucket in Nextcloud using its S3 backend, with the right endpoint, credentials, access scope, and verification steps.