Whitelabel Error Page: This application has no configured error view, so you are seeing this as a fallback.
Article ID: 422401
Updated On:
Products
Issue/Introduction
Applications fail to start with "Whitelabel Error Page" thrown by Spring Cloud Gateway.
Full error:
Whitelabel Error Page
This application has no configured error view, so you are seeing this as a fallback.
Environment
Spring Cloud Gateway upgrade from 2.3.3 to 2.3.4
Cause
When upgrading Spring Cloud Gateway (including minor upgrades), if the errand "Upgrade all service instances" errand is disabled e.g. Errands > Upgrade all service instances, service instances are not upgraded to the latest version of the installed (upgraded) tile. And while the gateway can start successfully, traffic will not be served properly, resulting in the 500 error.
"The upgrade-all-instances errand upgrades all existing Spring Cloud Gateway service instances to the version included in the latest installed tile."
Resolution
Enable all tile errands for Spring Cloud Gateway prior to running Apply Changes.
If the errand must otherwise remain disabled in your environment, ensure that it is either enabled during the upgrade or run manually after the Spring Cloud Gateway tile upgrade is complete.
Additional Information
Upgrade of Spring Cloud Gateway from version 2.3.3 to 2.3.4 include the following:
Enhancements included in this release
- Support for OpenAPI Parameters
- Update to Spring Boot 3.3.15
- Update to Spring Cloud 2023.0.8
- Update to Spring Cloud Gateway Server 4.1.11
- Update to OpenJDK 17.0.16+12
Security issues resolved in this release:
- CVE-2025-55163 (netty-codec-http2)
- CVE-2025-41243 (spring-cloud-gateway-server)
Although a minor release, it is therefore imperative that the errands are enabled during the tile upgrade or run immediately thereafter via bosh CLI.
Feedback
