No elasticsearch index gets created even though ES connection succeeds (no warnings in ES or diskover container log)

LSIO Discussion Container Support
1

On UNRAID 7.1.4
Using “Official” Elasticsearch version is 6.6.2 from Unraid Apps. Yes I created a new CA User Script named vm.max_map_count as directed.

Version: diskover-web v2.3.0 community edition (ce)
No completed indices found in Elasticsearch. Run a crawl and after it finishes reload select indices page.
Connected to ES: Yes
Last Update: Jul 24, 2025

Log:
Linuxserver.io version: v2.3.2-ls205
Build-date: 2025-07-24T11:14:03+00:00
───────────────────────────────────────
using keys found in /config/keys
[custom-init] No custom files found, skipping…
[ls.io-init] done.
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] done
usermod: no changes

NOTE: While trying (failing) to figure out where diskover gets the config params shown in its Settings, I noticed an oddity. Settings / Diskover Scan has a variable called PLUGINS_ENABLE (defaulted to “false”).
In diskover.py, there is a reference in load_plugins() to PLUGINS_ENABLE and another nearby in list_plugins() to PLUGINS_ENABLED. Note the difference (final “D”). Not saying its a bug, but I thought it suspicious in the context.
Anyway if you have a suggestion for troubleshooting my silent lack of index creation, please respond.

2

as a note, we support the container, not the application within the container. Diskover has its own developer and support capability. with that said, it is difficult for us to do much without seeing your docker compose or in the case of unraid users, the docker run.