WOPI discovery endpoint returns empty actions list (no docx/xlsx/pptx editors)

[oduchateau]

WOPI discovery endpoint returns empty actions list (no docx/xlsx/pptx editors)

Description

After enabling WOPI in local.json, the /hosting/discovery endpoint returns an XML response that contains only the <app> declarations and a single Capabilities action, but no actual editor actions (view, edit, etc.) for any file extension.

Steps to reproduce

1. Pull and run the latest image:

   docker pull ghcr.io/euro-office/documentserver:latest
   docker run -i -t -d -p 8080:80 --restart=always \
     -e EXAMPLE_ENABLED=true \
     -e JWT_SECRET=my_jwt_secret \
     ghcr.io/euro-office/documentserver:latest

2. Enable WOPI by editing /etc/onlyoffice/documentserver/local.json:

   {
     "wopi": {
       "enable": true
     }
   }

3. Restart services:

   docker exec <container> supervisorctl restart all

4. Query the discovery endpoint:

   curl http://localhost:8080/hosting/discovery

Expected result

A discovery XML containing actions for each supported extension, similar to upstream OnlyOffice:

<wopi-discovery>
  <net-zone name="external-http">
    <app name="Word" favIconUrl="...">
      <action name="view" ext="docx" urlsrc="https://.../hosting/wopi/word/view?..." />
      <action name="edit" ext="docx" requires="locks,update" urlsrc="https://.../hosting/wopi/word/edit?..." />
      <action name="convert" ext="doc" urlsrc="..." />
      ...
    </app>
    <app name="Excel" favIconUrl="...">
      <action name="view" ext="xlsx" urlsrc="..." />
      <action name="edit" ext="xlsx" requires="locks,update" urlsrc="..." />
      ...
    </app>
    ...
  </net-zone>
  <proof-key value="..." modulus="..." exponent="..." />
</wopi-discovery>

Actual result

<wopi-discovery>
  <net-zone name="external-http">
    <app name="Word" favIconUrl="https://.../web-apps/apps/documenteditor/main/resources/img/favicon.ico"/>
    <app name="Excel" favIconUrl="https://.../web-apps/apps/spreadsheeteditor/main/resources/img/favicon.ico"/>
    <app name="PowerPoint" favIconUrl="https://.../web-apps/apps/presentationeditor/main/resources/img/favicon.ico"/>
    <app name="Pdf" favIconUrl="https://.../web-apps/apps/pdfeditor/main/resources/img/favicon.ico"/>
    <app name="Capabilities">
      <action ext="" name="getinfo" requires="locks,update" urlsrc="https://.../hosting/capabilities"/>
    </app>
  </net-zone>
</wopi-discovery>

No actions are exposed for any actual file extension (docx, xlsx, pptx, etc.), making WOPI integration impossible — WOPI hosts cannot determine the URL pattern to invoke for editing or viewing documents.

The proof-key element is also missing.

Environment

• Image: ghcr.io/euro-office/documentserver:latest
• Build identifier visible in URLs: 9.2.1-09cfa1a0fe63716ad6884db689f9894a
• OS: Linux x86_64

Additional tests performed

• Same configuration applied directly to /etc/onlyoffice/documentserver/default.json (setting wopi.enable to true) produces the same incomplete discovery XML.
• The same local.json configuration on upstream onlyoffice/documentserver:latest produces a complete discovery XML with all expected actions and a proof-key element.
• WOPI is correctly enabled at the configuration level (the Capabilities action is rendered, suggesting the discovery generator runs but its action templates list is empty).
• This may be related to a missing template file or a build step that didn't generate the WOPI HTML templates referenced in default.json under wopi.htmlTemplate (../../web-apps/apps/api/wopi).

[SapuSeven]

I'm using the nightly image and the /hosting/discovery endpoint already returns a response without any additional configuration. But it's the same incomplete response like the "Actual result" above.

[MarcBrendel]

If you want to test WOPI, you can use a workaround for now. Add this to /etc/onlyoffice/documentserver/local-development-linux.json inside the container:

{
    "wopi": {
        "enable": true,
        "wopiZone": "external-http",
        "pdfView": ["djvu", "xps", "oxps"],
        "pdfEdit": ["pdf"],
        "forms": ["pdf"],
        "wordView": ["doc", "dotm", "dot", "fodt", "ott", "rtf", "mht", "mhtml", "html", "htm", "xml", "epub", "fb2", "sxw", "stw", "wps", "wpt", "pages"],
        "wordEdit": ["docx", "dotx", "docm", "odt", "txt"],
        "cellView": ["xls", "xlsb", "xltm", "xlt", "fods", "ots", "sxc", "xml", "et", "ett", "numbers"],
        "cellEdit": ["xlsx", "xltx", "xlsm", "ods", "csv"],
        "slideView": ["ppt", "ppsx", "ppsm", "pps", "potm", "pot", "fodp", "otp", "sxi", "dps", "dpt", "key"],
        "slideEdit": ["pptx", "potx", "pptm", "odp"]
    }
}

I agree that this should automatically be generated by a single environment variable though.