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

Aberta
#355 3 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
php
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
PHP
Estrelas
156
Forks
37
Merge médio
23h 51min
PRs com merge (30d)
2

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CollaboraOnline/richdocumentscode

Todas as issues de CollaboraOnline/richdocumentscode

Issues semelhantes

Mais issues de PHP

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.