did you figure out how to fix that? I just got the same thing, kinda funny though.
and it’s not related to xpack / elasticsearchy.yml, right? I certainly had it enabled.
in my case it already announced itself during the upgrade with kibana not recognizing some fields and thus failing to start. I had to allow it to delete them, but effectively the problem was in whatever caused it to no longer work with elastic security and not my step that allowed it to start.
(would be nice if things wouldn’t always fail so fatally)
if you set ‘security’ as ‘solution view’ you get an near empty UI.
if you go back to the main URI, you get
Application Not Found
No application was found at this URL. Try going back or choosing an app from the menu.
It’s no longer possible to access stack management then. But you can still move backwards via the browser.
once you set the UI to ‘classic’ again, you’ll find that suddenly observability is no longer selected. so there’s some ripple damage kind of problems here.
tl;dr: something lets you lose the application thinggy as a whole.
- xpack.security.enabled in elasticsearch.yml is related but it does happen when it's set in elasticsearch.yml
- kibana.yml: must also have the setting but doesn't like it (
kibana | FATAL Error: [config validation of [xpack.security].enabled]: definition for this key is missing, no longer needed as per FATAL Error: [config validation of [xpack.security].enabled]: definition for this key is missing - #2 by TimV ) - happens with clusters used for endpoint security alone, so where you’d have no manually defined elements at all
- reinstall the Elastic Defend integration / assets: no effect
- migrations.discardCorruptObjects: "8.18.5" / migrations.discardUnknownObjects: "8.18.5" help to unbreak kibana but don’t solve issue
- migration issue: possible but should not kill a security solution
- version: not related to 9.x but related to very recent versions
- plugins / integrations: stay in place, seem functional
- feature itself: leaves no forwarding address
- integrations -> elastic security: might be missing! -> add elastic security -> install 3 assets
- still missing in spaces->feature visibilty
- independently of that, certainly need to attach to agent policy
- need to re-configure api access too, take a break since that looks like a nightmare
- can't be the whole issue, at least the empty menu and dashboard should exist without data
please check if you also got these errors, or WHICH of them you do
kibana | [2025-08-13T01:34:38.191+00:00][ERROR][plugins.osquery] Not starting transform osquery_manager.action_responses-default-0.0.1 since it's state is: failed
kibana | [2025-08-13T01:34:38.211+00:00][ERROR][plugins.cloudSecurityPosture] Failed to update index [Name: logs-cloud_security_posture.scores-default]
kibana | [2025-08-13T01:34:38.211+00:00][ERROR][plugins.cloudSecurityPosture] ResponseError: illegal_argument_exception
kibana | [2025-08-13T02:01:07.185+00:00][ERROR][plugins.osquery] Not starting transform osquery_manager.action_responses-default-0.0.1 since it's state is: failed
kibana | [2025-08-13T02:01:07.197+00:00][ERROR][plugins.cloudSecurityPosture] Failed to update index [Name: logs-cloud_security_posture.scores-default]
kibana | [2025-08-13T02:01:07.197+00:00][ERROR][plugins.cloudSecurityPosture] ResponseError: illegal_argument_exception
kibana | [2025-08-13T02:03:09.614+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:09.617+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:10.836+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:12.921+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:13.093+00:00][ERROR][plugins.fleet] Error: Saved object [epm-packages/elastic_security] not found
kibana | [2025-08-13T02:03:17.001+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:25.151+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:41.309+00:00][ERROR][plugins.fleet] [elastic_security] package not installed or found in registry
kibana | [2025-08-13T02:03:58.872+00:00][ERROR][savedobjects-service.importer] Failed to import saved objects. 2 errors: [{"type":"index-pattern","id":"logs-*","meta":{"title":"logs-*"},"error":{"type":"conflict"}},{"type":"index-pattern","id":"metrics-*","meta":{"title":"metrics-*"},"error":{"type":"conflict"}}]
-> gave it another hard look and then wiped it all.