If the server running ONLYOFFICE is out of space, it won't be able to create the temporary cache files needed to open your document. If you'd like to dive deeper into a specific setup: Server environment (e.g., Docker, Ubuntu, Windows) Integration platform (e.g., Nextcloud, WordPress, Alfresco) Log error snippets
Ensure both your Document Server and your connector app (Nextcloud/ownCloud app) are on compatible versions. If the server running ONLYOFFICE is out of
If you get a timeout or a certificate error here, ONLYOFFICE definitely can't reach your files. Step 3: Adjust the Connector Settings If you are using Nextcloud: Go to > ONLYOFFICE . Check the Document Editing Service address . Step 3: Adjust the Connector Settings If you
Look for "Error: self signed certificate" or "Error: connect ECONNREFUSED." Step 2: Test Internal Accessibility curl -I https://your-nextcloud-domain
Log into your server via SSH and try to curl the document URL directly. curl -I https://your-nextcloud-domain.com Use code with caution.
The most common culprit. If your Document Server (DS) and your web platform (e.g., Nextcloud) are on the same server but use self-signed certificates, they may refuse to "talk" to each other.
If you are seeing the error you are likely dealing with a communication breakdown between your document server and your storage backend (like Nextcloud, ownCloud, or Seafile).