Eldric Docs 5.0.177 ← eldric.ai
Operations

Install troubleshooting

Operations · Cluster administrators · Applies to 5.0.x

Use this page when installation, first admin setup or first public API checks do not behave as expected.

On this pageChecklistCommon symptoms

Checklist

  1. Confirm the supported package repository at repo.eldric.ai is reachable from the host.
  2. Confirm the installed package version matches the intended 5.0.x line.
  3. Confirm DNS and TLS for the public entry point before testing browser or API clients.
  4. Confirm the first administrator flow has completed once and is not being repeated by another user.
  5. Confirm the license file or evaluation mode matches the intended tier.
  6. Confirm the public health endpoint responds before testing higher-level workflows.

Common symptoms

The first four checks, with the commands

Each of these answers one question and needs nothing installed but curl. Run them in order — the first that fails is where the problem is.

  1. Is the repository reachable and a valid dnf repo?
    curl -fsS https://repo.eldric.ai/5.0/repodata/repomd.xml > /dev/null && echo ok
    Anything other than ok is a network or proxy problem, not a package problem.
  2. Is this OS supported? Eldric is supported on Fedora 43 and Fedora 44, on x86_64 and aarch64; the GPU package is built for Fedora 43 on x86_64. Fedora 42 and RHEL-family systems (RHEL, CentOS Stream, Rocky, Alma) are not supported at the moment; on them the installer exits 2 and says which release it found. If Eldric was installed on one of them, it is probably an old version; check with rpm -q eldric-aios.
    . /etc/os-release; echo "$ID $VERSION_ID"
  3. Is the daemon actually up?
    curl -fsS http://localhost:8880/health
    It reports the running version. If this answers, the install worked and the problem is in front of the daemon — TLS, hostname or routing.
  4. Is a 401 about the key or the session?
    curl -fsS -H "X-API-Key: <key>" http://localhost:8880/api/v1/auth/whoami
    A successful reply lists the scopes that key actually carries; comparing them with the scope the endpoint needs turns a 401 into a specific answer.

Every command above is read-only and safe to run on a production node.

SymptomLikely next step
Package install failsCheck repository reachability, OS support and package signature trust.
Cannot sign in to /adminThe admin console has no login until the first user exists. Create it in the chat at https://<host>/chat: the first person to register there becomes superadmin, and that account signs in to /admin. The password given to eldric setup is not a login. See admin guide, Day 1.
Browser cannot open chatCheck hostname, TLS and public route.
API returns 401Check API key, session state and tenant scope.
RAG upload succeeds but no citations appearCheck indexing status and selected knowledge base.
macOS package warningFrom 5.0.167 the macOS package is signed with an Apple Developer ID and notarised, so Gatekeeper opens it without a warning. Packages up to 5.0.160 were not signed and do warn. For those, the warning reports the missing signature, not a damaged download. If a 5.0.167 or later package warns, do not override it. Check that it came from repo.eldric.ai and contact office@eldric.ai.
/health or the chat API answers 401 from outside after upgrading to 5.0.168Expected. From 5.0.168, /health, /metrics, /v1/chat/completions, /v1/embeddings and a few other operational paths need a login when the request comes through the public edge. On the host itself, curl http://localhost:8880/health still answers without one. If they still answer anonymously from outside, your reverse proxy is not setting X-Eldric-Public-Edge. See the 5.0.168 release notes.
An integration inside your network gets 401 from chat or embeddings after upgrading to 5.0.170Expected, and breaking. From 5.0.170, /v1/chat/completions, /v1/completions and the three /embeddings paths need an API key or session from every caller, including callers on your LAN or on port 8880 directly. Give the integration an X-API-Key. /v1/models still answers without one.

For unresolved install issues, contact office@eldric.ai with version, operating system, deployment shape and the redacted error message.