Repository navigation
Replies: 2 comments
[AIO v15.1.0 Beta] Euro-Office returns 502 Bad Gateway after upgrade despite healthy containers and working internal healthchecksDescribe the bugAfter upgrading my existing Nextcloud AIO installation to v15.1.0 Beta, Euro-Office stopped working. Euro-Office worked correctly on previous AIO versions with the same deployment and reverse-proxy configuration. The issue appeared immediately after upgrading to v15.1.0 Beta. All AIO containers, including I performed several connectivity tests, which confirm that Euro-Office is accessible both directly through the internal Docker network and through the AIO Apache container. The problem occurs when Nextcloud accesses Euro-Office through the public HTTPS endpoint. Steps to reproduce
Expected behaviorEuro-Office should continue working normally after upgrading AIO. Nextcloud Office should successfully communicate with the Euro-Office document server through the Actual behaviorNextcloud Office reports:
The Nextcloud logs also report a server exception related to the Euro-Office healthcheck:
Despite this error, Docker reports the Euro-Office container as healthy. Environment
Diagnostic results1. Container health statusThe following AIO containers are reported as healthy:
There are no obvious container startup failures. 2. Euro-Office container logsCommand executed: Relevant output:
The container also reports warnings related to Tini and Supervisord, but no obvious service startup failures. 3. Direct Euro-Office connectivity testI tested connectivity directly from the Nextcloud container to Euro-Office over the internal Docker network. Command: Result: The Euro-Office healthcheck endpoint is reachable directly from the Nextcloud container. 4. Connectivity through AIO ApacheI also tested the Euro-Office healthcheck through the AIO Apache container. Command: Result: The AIO Apache container successfully forwards the internal healthcheck request to Euro-Office. 5. Public HTTPS endpointDespite both internal connectivity tests succeeding, Nextcloud Office continues to report:
Summary of diagnostic results
Additional contextThis behavior started immediately after upgrading to AIO v15.1.0 Beta. Euro-Office was functioning correctly on previous AIO versions, and the deployment environment and external reverse-proxy configuration remained unchanged. The diagnostic results suggest that the Euro-Office container itself is operational and that basic internal routing through AIO Apache works. However, requests through the public HTTPS endpoint fail with HTTP 502. This appears to be a possible regression in AIO v15.1.0 Beta, potentially affecting Euro-Office integration or HTTP proxy routing. The exact cause has not yet been identified. Could you please investigate whether any changes introduced in AIO v15.1.0 Beta could explain this behavior? Related reportsThese reports may describe related Euro-Office connectivity problems, although I cannot confirm that they have the same underlying cause. |
Additional finding: Collabora works correctlyAs an additional test, I disabled Euro-Office in Nextcloud AIO and enabled Collabora instead. After starting Collabora, Nextcloud Office connected successfully, and everything works without any issues. This confirms that the same Nextcloud AIO installation and existing reverse-proxy configuration work correctly with Collabora. The issue appears to be specific to Euro-Office in AIO v15.1.0 Beta, rather than a general problem with Nextcloud Office or the deployment environment. No changes were made to the external reverse-proxy configuration. |
Uh oh!
There was an error while loading. Please reload this page.
Nextcloud 35.0.3 is included
What's Changed
🏕 New features and other improvements
🐞 Fixed bugs
👒 Updated dependencies
📄 Improved documentation
New Contributors
Full Changelog: v15.0.2...v15.1.0
This discussion was created from the release v15.1.0 Beta.
All reactions