Built-in CODE 26.4.402 fails to open documents with "System exception"; downgrade to 26.4.303 fixes it
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- PHP
- Estrellas
- 156
- Forks
- 37
- Merge medio
- 23 h 51 min
- PR fusionados (30 d)
- 2
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CollaboraOnline/richdocumentscode
-
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
-
Export to PDF uses wrong localeAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
CollaboraOnline/richdocumentscode#339 · 2 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 43/100
CollaboraOnline/richdocumentscode#338 · 1 comentario ·
-
Server audit alertsAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
CollaboraOnline/richdocumentscode#337 · 5 reacciones ·
Todos los issues de CollaboraOnline/richdocumentscode
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
vimeo/psalm#14139 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
sync-en
Dificultad 1/5 1-3 horas Aptitud para principiantes 79/100
Los mantenedores suelen responder en 1 día
-
wpvc
Dificultad 1/5 1-3 horas Aptitud para principiantes 67/100
10up/simple-local-avatars#386 ·
-
not confirmed
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Bug (unconfirmed) Documentation :books:
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
FreshRSS/FreshRSS#9577 · 4 comentarios ·
Los mantenedores suelen responder en 1 día