Built-in CODE 26.4.402 fails to open documents with "System exception"; downgrade to 26.4.303 fixes it
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 48/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- PHP
- Sterne
- 156
- Forks
- 37
- Ø Merge
- 23 Std. 51 Min.
- Gemergte PRs (30 T.)
- 2
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus CollaboraOnline/richdocumentscode
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 38/100
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 48/100
CollaboraOnline/richdocumentscode#339 · 2 Kommentare ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 43/100
CollaboraOnline/richdocumentscode#338 · 1 Kommentar ·
-
Server audit alertsOffen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
CollaboraOnline/richdocumentscode#337 · 5 Reaktionen ·
Alle Issues in CollaboraOnline/richdocumentscode
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
vimeo/psalm#14139 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
sync-en
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 79/100
Maintainer antworten meist innerhalb von 1 Tag
-
wpvc
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 67/100
10up/simple-local-avatars#386 ·
-
not confirmed
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
Bug (unconfirmed) Documentation :books:
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
FreshRSS/FreshRSS#9577 · 4 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag