Whitelabel Error Page — This application has no explicit mapping for /error
Spring Boot’s default error page — the request hit no controller mapping (404) or a controller threw (500).
Whitelabel Error PageThis application has no explicit mapping for /error Meaning
The status line under the heading tells you which: 404 means no handler mapped that path (wrong URL, controller not scanned, @Controller vs @RestController); 500 means an exception — check the logs.
Common causes
- No controller for the path / wrong HTTP method
- Controller outside the component-scan package
- @Controller returning a view name that doesn’t exist
- Exception in the handler (status 500)
⚡ Quick fix
- Check the status shown on the page
- Verify @RequestMapping paths and package location
- Use @RestController for JSON APIs
- Read the server log for 500s
Detailed fix by platform
Java
- Add
server.error.include-message=alwaystemporarily in dev to see details
How to diagnose
- Status — 404 or 500?
- Mapping — Does a handler match path + method?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Java
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026