Built-in CODE 26.4.402 fails to open documents with "System exception"; downgrade to 26.4.303 fixes it
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- PHP
- Stelle
- 156
- Fork
- 37
- Merge medio
- 23h 51m
- PR unite (30g)
- 2
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di CollaboraOnline/richdocumentscode
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
CollaboraOnline/richdocumentscode#339 · 2 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 43/100
CollaboraOnline/richdocumentscode#338 · 1 commento ·
-
Server audit alertsAperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
CollaboraOnline/richdocumentscode#337 · 5 reazioni ·
Tutte le issue di CollaboraOnline/richdocumentscode
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
vimeo/psalm#14139 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
sync-en
Difficoltà 1/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno
-
wpvc
Difficoltà 1/5 1-3 ore Idoneità per principianti 67/100
10up/simple-local-avatars#386 ·
-
not confirmed
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
Bug (unconfirmed) Documentation :books:
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
FreshRSS/FreshRSS#9577 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno