BootUI
Try it
Setup
Features
Properties
AI agents
Ecosystem
GitHub
Try it
Setup
Features
Properties
AI agents
Ecosystem
GitHub
  • Get started

    • Try the sample app
    • Setup
    • Spring WebFlux
    • Quarkus
    • Activation and safety
    • Non-standard runtimes
    • Troubleshooting
  • Features

    • All features
    • Overview
    • Advisors
    • Runtime
    • Configuration
    • Database
    • Security
    • Services
    • Diagnostics
    • Developer tools
  • Reference

    • Properties
    • Framework support
    • AI agents
    • Command line
    • BootUI family
  • Diagnostic checks

    • Architecture
    • REST API
    • Spring
    • Hibernate
    • Database
    • Security
    • Memory
    • Pentesting
    • GraalVM readiness
    • CRaC readiness
    • Quarkus
    • Quarkus security
  • Contributing

    • Repository
    • Specification
    • Implementation plan
    • Quarkus design notes
    • WebFlux design notes
  • Privacy

Troubleshooting

SymptomCheck
BootUI path returns 404Use the dev or local profile, add DevTools, or set bootui.enabled=ON; then open the configured bootui.path (default /bootui). In application.yml, bootui.enabled: ON is valid — YAML parses it as a boolean, which BootUI accepts as ON.
BootUI is disabled in prodThis is intentional; only bootui.enabled=ON can force activation with a disabled profile.
Command-line app now stays upExpected: BootUI starts a servlet server so the console is reachable. Set bootui.force-web=false to keep the app non-web.
Browser is rejectedBootUI accepts loopback callers and fails closed for everything else. Inside a container, set bootui.trust-container-gateway=AUTO to auto-detect and trust the default gateway /32 (the SNAT source of published-port traffic) — no subnet needed on any Docker flavor, and the Host + CSRF protections stay on. For a custom proxy/bridge or LAN access, add that source range to bootui.trusted-proxies instead — 172.16.0.0/12 on Linux Docker Engine, 192.168.65.0/24 on Docker Desktop (macOS/Windows) — plus the hostname you browse with to bootui.allowed-hosts. Use bootui.allow-non-localhost=true only as a blunt last resort on a trusted local network.
Spring Security blocks UIBootUI auto-registers a permit-all chain for the configured UI/API paths when Spring Security is active; check for a custom higher-priority chain.
localhost redirected you too many timesBootUI serves the console at both /bootui and /bootui/ with no redirect, so a host trailing-slash–stripping filter or proxy (e.g. Spring's UrlHandlerFilter.trailingSlashHandler("/**").wrapRequest(), a standard Boot 4 idiom) can't loop on it. If you still hit this on an older BootUI, upgrade or open /bootui/ (with the trailing slash) directly.
A panel is emptyEnable the relevant Actuator endpoint or optional Spring module; BootUI degrades to stable empty DTOs when data is unavailable.
Startup Timeline is emptyLeave bootui.startup.enabled=true and bootui.startup.capacity greater than zero, or provide your own BufferingApplicationStartup.
Secrets are hiddenDefault exposure is MASKED; use METADATA_ONLY to hide all values or FULL only in trusted local sessions.
Static resources disabledspring.web.resources.add-mappings=false is bypassed by BootUI: it registers its own handler at the configured bootui.path for dashboard assets and logs a WARN line; the host's other static resources stay disabled.
Prev
Non-standard runtimes