Spring Boot refuses to start: wrong Spring Cloud release train
APPLICATION FAILED TO STARTShort answer
Spring Cloud checks the Spring Boot version on the classpath at startup and stops the app when the pairing is wrong. Pick the release train from Spring's compatibility table for your Boot generation, or move Boot to a generation your train supports.
Fix it fast
1Find out which cause you have
Read the two versions that matter: the Boot version in the report and the Spring Cloud BOM version in your build.
./gradlew dependencies --configuration runtimeClasspath | grep -i "spring-cloud-dependencies\|spring-boot-starter "2Match what you see, then jump to its fix
- 1
The report names your Boot version and suggests other versions in its Action section.The release train does not match the Boot generationFix - 2
The build used to work and broke only after a Spring Boot version change.You upgraded or downgraded Boot and left the train behindFix - 3
You have tested your setup and the verifier is the only thing in the way.You accept the risk and want to bypass the checkFix
- 1
What does the error look like?
APPLICATION FAILED TO STARTYour project setup is incompatible with our requirements due to following reasons:Spring Boot [2.7.0] is not compatible with this Spring Cloud release train
Cause 1 of 3
The release train does not match the Boot generation
1Check
Look your Boot generation up in the release train table of the Spring Cloud project page. For example, 2021.0.x pairs with Boot 2.6.x and 2.7.x (2.7.x from 2021.0.3), 2023.0.x with 3.2.x and 3.3.x, and 2025.0.x with 3.5.x.
grep -rn "springCloudVersion\|spring-cloud-dependencies" build.gradle* gradle/libs.versions.toml2Fix
Change the Spring Cloud BOM version to a train that supports your Boot generation. Note that Boot 2.7.0 needs 2021.0.3 or later of the train, not an earlier 2021.0.x release.
ext {
set('springCloudVersion', "2021.0.3")
}
dependencyManagement {
imports {
mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
}
}3Verify
Start the application again.
./gradlew bootRunConfirmed by spring.io
Cause 2 of 3
You upgraded or downgraded Boot and left the train behind
1Check
Each Spring Cloud train lists one or two supported Boot generations on the project page, so a Boot upgrade usually needs a new train.
grep -n "org.springframework.boot" build.gradle*2Fix
Move the train and Boot together. If you must keep the train, change Boot to one of the versions that the Action section of the report lists.
plugins {
id 'org.springframework.boot' version '3.5.0'
}
ext {
set('springCloudVersion', "2025.0.0")
}3Verify
Run the tests and start the application.
./gradlew test bootRunConfirmed by spring.io
Cause 3 of 3
You accept the risk and want to bypass the check
1Check
The verifier only looks at the Spring Boot version. Spring Cloud Commons documents a property that turns it off and one that sets your own list of accepted versions.
grep -rn "compatibility-verifier" src/main/resources2Fix
Set the property, preferably the list of accepted Boot versions rather than turning the check off.
# application.properties
spring.cloud.compatibility-verifier.compatible-boot-versions=3.5.x
# or switch the check off
spring.cloud.compatibility-verifier.enabled=false3Verify
Start the application.
./gradlew bootRunConfirmed by docs.spring.io
How do I stop it coming back?
- Import the Spring Cloud BOM once, and change the train and Boot in one commit.
- Check the compatibility table before accepting an automated Boot version bump.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Nuclear Home VideoA video-streaming Android app built from scratch, engineered for smooth playback.
Related fixes
Back end
A scanner flags jackson-databind: how to upgrade it in Gradle
jackson-databind vulnerability reported by a dependency scanner
Find where the old jackson-databind comes from, then raise it.
3 causes, each with a fixBack end
Gradle cannot resolve spring-boot-gradle-plugin after a Spring Boot 3 upgrade
Plugin [id: 'org.springframework.boot', version: '3.0.1'] was not found in any of the following sources
Spring Boot 3 needs Java 17 or newer and a recent Gradle, and its Gradle plugin is published on the Gradle Plugin Portal.
3 causes, each with a fixBack end
bootJar cannot find the main class of a Spring Boot project
Main class name has not been configured and it could not be resolved
The Spring Boot Gradle plugin looks in the main source set's output for a class with a public static void main method.
2 causes, each with a fixBack end
Spring Boot fails at startup with an error processing a condition on an auto-configuration
java.lang.IllegalStateException: Error processing condition on org.springframework.boot.autoconfigure.jdbc.JndiDataSourceAutoConfiguration
This message only says Spring Boot failed while evaluating an auto-configuration condition.
3 causes, each with a fixBack end
Swagger UI URL shows the Whitelabel Error Page in Spring Boot
Whitelabel Error Page when opening /swagger-ui.html
The Whitelabel page means Spring found no handler for that address.
3 causes, each with a fixBack end
Spring Boot will not start because port 8080 is already taken
Action: Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.
Spring Boot listens on 8080 unless told otherwise, and only one process can own a port.
3 causes, each with a fix