ONLYOFFICE Community Edition save/download failures and Tomcat integration issues after custom port deployment on Windows Server

Docs
1

Full Problem Description

I have deployed the community edition of ONLYOFFICE on a Windows Server environment, with the following setup:

  • Changed ONLYOFFICE’s default port from 80 to 88

  • Opened port 88 for public access

  • Mapped the server’s internal IP to a public IP address

  • The ONLYOFFICE example page loads successfully from the external network

However, I am encountering two critical issues:

  1. When editing documents in ONLYOFFICE, I receive the following errors:

    • A warning that the document could not be saved, prompting me to download the file

    • A subsequent error stating that the download failed, forcing me to close the editor

  2. My Tomcat web application (hosted on the same server as ONLYOFFICE, with its own port also mapped to the public network and accessible externally) cannot make successful API calls to ONLYOFFICE.

I would appreciate any guidance on resolving these connectivity and integration problems.

2

maybe the callback api return false

3

Hi @huawushuang, checking in on this one!

@zhcngu is pointing in the right direction — the save/download errors and Tomcat API failures usually come from Document Server blocking its own outbound requests to private IP addresses (192.168.x.x, 10.x.x.x) by default. The example page loads fine because that’s a browser → DS request, but the save flow needs DS to reach back to your integrator, and that’s where it gets blocked.

On a Windows install, open:

%ProgramFiles%\ONLYOFFICE\DocumentServer\config\local.json

And add (merging with anything already there):

json

{
  "services": {
    "CoAuthoring": {
      "request-filtering-agent": {
        "allowPrivateIPAddress": true,
        "allowMetaIPAddress": true
      }
    }
  }
}

Then restart the ONLYOFFICE services from services.msc. That should fix both the editor save and the Tomcat calls in one go.

Let us know how it goes — or if you’ve already got it working!