Check: Master key header. Fix: Retrieve the key (above) and send it as a Bearer token — there is no keyless mode on this image.

Service inactive on first boot

Check: systemctl status meilisearch-firstboot. Fix: Key generation must complete once; check /etc/meilisearch.env exists and re-start meilisearch.

Index size growing fast

Check: Snapshot/dump directories on the same volume. Fix: Ship dumps off-box and prune; grow the volume as needed.

Troubleshoot Meilisearch (Hardened) — DC Associates Group Docs

Symptom	Check	Fix
401 on every request	Master key header	Retrieve the key (above) and send it as a Bearer token — there is no keyless mode on this image.
Service inactive on first boot	systemctl status meilisearch-firstboot	Key generation must complete once; check /etc/meilisearch.env exists and re-start meilisearch.
Index size growing fast	Snapshot/dump directories on the same volume	Ship dumps off-box and prune; grow the volume as needed.

Logs & useful commands

journalctl -u meilisearch -f
Health: curl -s http://127.0.0.1:7700/health → {"status":"available"}
First boot state: meilisearch-firstboot.service creates /etc/meilisearch.env with the per-instance master key (ConditionPathExists guard), then the service starts. Health endpoint answers within seconds.

Still stuck? Email support@dcassociatesgroup.com with the product name, cloud + region, instance size, and the output of the health command — first response within 1 business day, most tickets same-day.