Built-in CODE 26.4.402 fails to open documents with "System exception"; downgrade to 26.4.303 fixes it

オープン
#355 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
php
領域
backend

調査の方向性

Start by tracing the built-in proxy path for the failing POST to proxy.php?req=/cool/ws?WOPISrc=... and compare its handling in versions 26.4.402 and 26.4.303. The report also points to COOLWSD session startup and the WOPI settings endpoint; inspect their logs and request handling first. Done means documents open with 26.4.402 in the reported subdirectory setup, without changing the server configuration.

索引モデルが issue の本文から書いたものです。

説明

After upgrading the Nextcloud built-in CODE server (richdocumentscode) from 26.4.303 to 26.4.402, Nextcloud Office can no longer open documents.

The browser reports:

Socket connection could not be established or the socket connection was unexpectedly closed. The reverse proxy may be misconfigured.

The setup was working correctly before the update. No Apache, PHP or Nextcloud configuration was changed.

Downgrading only richdocumentscode from 26.4.402 back to 26.4.303 immediately fixes the problem.

Environment

Nextcloud: 34.0.4

richdocuments: 11.1.1

Broken: richdocumentscode: 26.4.402 / CODE 26.04.4.2

Working: richdocumentscode: 26.4.303

Web server: Apache

PHP: 8.3.35

Built-in CODE server (richdocumentscode), no separate Collabora reverse proxy

Nextcloud installed in a subdirectory:
https://example.org/owncloud/

What works with 26.4.402

The built-in CODE server starts normally.

The status endpoint responds with HTTP 200:

/owncloud/apps/richdocumentscode/proxy.php?status

WOPI discovery through the built-in proxy also works:

/owncloud/apps/richdocumentscode/proxy.php?req=/hosting/discovery

CODE can contact the Nextcloud WOPI endpoints and retrieve document information/content.

What fails

When opening a document, the browser sends a request through the built-in proxy similar to:

POST /owncloud/apps/richdocumentscode/proxy.php?req=/cool/ws?WOPISrc=...

This returns:

HTTP 400 Bad Request

The response body is empty.

The COOLWSD log then repeatedly contains:

ERR Failed to add session to [...] with URI [...]: System exception
ERR Error while starting session on [...] for socket #... Terminating connection. Error: System exception
ERR Failed to get settings json from [.../apps/richdocuments/wopi/settings?type=userconfig&...] with status[]
ERR Failed to load all settings from [.../apps/richdocuments/wopi/settings?type=userconfig&...]
WRN Unassociated Kit (...) disconnected unexpectedly
WRN Unknown Kit process closed with pid -1

There is also:

WRN subForKit shared-https_example.org/owncloud/index.php/apps/richdocuments/wopi/settings-...
not responsive for 4012559ms while spawning. Resetting.

The running built-in COOLWSD process is started with the expected proxy configuration, including:

--port=9983
--o:ssl.enable=false
--o:net.proxy_prefix=true

Reproduction

Run Nextcloud 34.0.4 with:

richdocuments 11.1.1

richdocumentscode 26.4.402

Open an Office document.

The editor fails to connect and the /cool/ws request through proxy.php returns HTTP 400.

Disable richdocumentscode.

Replace 26.4.402 with 26.4.303.

Enable richdocumentscode again.

Open the same document.

Result after downgrade

With:

richdocuments: 11.1.1
richdocumentscode: 26.4.303

the same documents open normally again.

No Apache, Nextcloud, PHP or reverse-proxy configuration was changed between the failing and working tests.

Therefore this appears to be a regression introduced between richdocumentscode 26.4.303 and 26.4.402 / CODE 26.04.4.2, specifically affecting the built-in CODE server/proxy setup.

Please let me know if a debug-level COOLWSD log or additional configuration information would be useful.

主要言語
PHP
スター
156
フォーク
37
平均マージ
23時間 51分
マージ済み PR(30日)
2

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CollaboraOnline/richdocumentscode のほかの issue

CollaboraOnline/richdocumentscode の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。