I am experiencing an intermittent problem with ONLYOFFICE Document Server running on a Linux server that is integrated with my website for editing and viewing office documents. The integration generally works as expected, and users can open documents from the website and work with them in the ONLYOFFICE editor. However, after the service has been running for some time, certain document-opening requests occasionally fail before the editor finishes loading. In these cases, the user may see a loading screen that never completes or an error indicating that the document could not be opened, even though the same document may work normally when the user tries again later. The issue is difficult to reproduce consistently because it does not affect every document or every session, and the website itself remains accessible when the editor fails. I am trying to determine whether the problem originates in the communication between my website and ONLYOFFICE Document Server, or whether a Linux service or process involved in document conversion and loading is becoming unavailable intermittently. I would appreciate guidance from anyone who has experienced similar behavior with a self-hosted ONLYOFFICE installation on Linux.
The problem is particularly confusing because the affected documents are stored and managed through the website, while ONLYOFFICE Document Server is responsible for providing the editing interface. When a user selects a document, the website generates the configuration required to open it and passes the relevant document information to the editor. During a failed attempt, the editor begins loading but does not reach the normal editing screen. In some cases, the failure appears to occur before the document contents become visible, while in other cases the loading process continues for a while before an error is displayed. I have checked whether the original files are still present and accessible through the website, and the problem does not appear to be caused by every document being missing or corrupted. I am unsure whether the editor is failing to retrieve a document from the website, whether the Document Server cannot complete its internal processing, or whether a communication request between the two components is timing out. I want to identify the precise stage at which the opening process stops rather than treating every failed session as a general document-loading error.
I have started reviewing the Linux services involved in the installation and checking their status when the issue occurs. The Document Server services may appear to be running even when a user reports that a document will not open, so simply confirming that the processes exist has not been enough to explain the behavior. I would like to understand which service logs provide the most useful information about failed editor sessions, document retrieval, conversion requests, and communication between the website and Document Server. I am also checking whether the errors reported by the browser correspond to anything recorded in the Linux system logs at the same time. If a document-opening request fails at a particular timestamp, I want to be able to follow that event through the website’s logs and the Document Server logs to determine whether the request reached the expected component and how it was handled. I have not identified a single service or process responsible for the failure, and I would prefer to gather more specific evidence before restarting services or changing the installation configuration.
Another area I am investigating is whether the problem could be related to the resources available to the Linux server while documents are being opened. The installation handles requests from multiple users, and I want to determine whether a failed opening attempt coincides with increased memory usage, CPU load, process limits, or a temporary shortage of available resources. I understand that a service can remain active while individual operations fail because a dependency or resource has become unavailable, but I have not established that resource pressure is involved in my case. I would appreciate advice on which metrics should be collected during a successful session and a failed session, and whether ONLYOFFICE provides specific logs or diagnostic indicators for document-opening and conversion failures. I am particularly interested in knowing how to distinguish a resource-related failure from a problem involving document URLs, access permissions, or internal service communication. A clear diagnostic approach would help me avoid increasing server resources unnecessarily if the actual cause is a configuration or request-handling issue.
I would also like to verify that the connection between my website and ONLYOFFICE Document Server follows the expected configuration for a self-hosted Linux deployment. I am reviewing the document URL supplied to the editor, the accessibility of that URL from the Document Server environment, and the configuration used to establish communication between the application and the editor. A document that is accessible from a user’s browser is not necessarily accessible from the server that needs to retrieve it, so I want to confirm that the relevant network requests succeed from the correct environment. I am also interested in whether expired document links, callback configuration, reverse-proxy behavior, or request timeouts could cause the editor to begin loading but fail before the document becomes available. These are possibilities I would like to test rather than confirmed causes. If there is a recommended checklist for diagnosing document-opening failures in a Linux-hosted ONLYOFFICE integration, I would appreciate knowing which checks should be performed first and how to interpret the results without changing several configuration settings at once.
Has anyone in the ONLYOFFICE community encountered intermittent document-opening failures with Document Server installed on Linux, where the website remains available and the same documents sometimes open successfully after another attempt? I would appreciate recommendations for tracing a failed session across the website, browser, and Document Server, particularly which logs and error details are most useful for identifying the component responsible. If necessary, I can provide the Linux distribution, ONLYOFFICE Document Server version, deployment method, relevant service-log excerpts, browser console errors, and timestamps for successful and unsuccessful attempts. I can also test whether the failure can be reproduced with a particular document and share the results of checking its accessibility from the Document Server environment. My goal is to identify and correct the underlying reason that document-opening requests intermittently fail, rather than relying on repeated retries or restarting services without knowing what went wrong. Any practical troubleshooting suggestions specific to ONLYOFFICE on Linux would be greatly appreciated. Sorry for very long post!