Install troubleshooting

When the installer
doesn't go quietly.

Nine common failure modes during install or first launch, with the recovery for each. If your error isn't covered here, the platform's own logs are usually the next port of call — journalctl -u eldric-aios --since "10 min ago" shows what failed and why.

1. curl: command not found

The base distribution doesn't have curl. Install it first, then re-run the bootstrap:

sudo dnf install curl
curl -fsSL https://repo.eldric.ai/install.sh | sudo bash

2. GPG check FAILED

The Eldric signing key wasn't imported (the bootstrap script normally handles this). Import manually, then retry:

sudo rpm --import https://repo.eldric.ai/signing/RPM-GPG-KEY-eldric
sudo dnf install eldric-aios

3. No package eldric-aios available

The repository file wasn't installed, or dnf didn't see it. Confirm the repo is registered:

sudo dnf repolist | grep eldric

If nothing matches, re-run the bootstrap script. If the repo is listed but the package isn't found, your dnf cache is stale: sudo dnf clean all && sudo dnf makecache.

4. Port 443 already in use

Another service (most often nginx or Apache) is bound to TCP 443. Two options:

• Stop the conflicting service if it's no longer needed: sudo systemctl stop nginx && sudo systemctl disable nginx
• Change Eldric's port by editing /etc/eldric/eldric-aios.env and setting ELDRIC_EDGE_HTTPS_PORT=8443. Restart: sudo systemctl restart eldric-aios.

5. Cannot open /chat — connection refused

The daemons need a few seconds to come up. Wait thirty seconds after install, then check:

sudo systemctl status eldric-aios
journalctl -u eldric-aios --since "5 min ago" --no-pager | tail -40

If the unit is active (running) but the port is silent, a firewall is most likely blocking it: sudo firewall-cmd --add-service=https --permanent && sudo firewall-cmd --reload.

6. Admin signup says “an admin already exists”

Someone on the network signed up first. The admin role is locked to the first signup on a fresh cluster. Three paths:

• Have the existing admin add you from Admin Console → Users.
• If the wrong person claimed admin by accident, the existing admin can reassign the role to you and downgrade themselves.
• Last resort on a clean install you control: stop the service, wipe /var/lib/eldric/controller/users.db, restart, sign up again. This destroys all users and tenants; never do it on a production cluster.

7. License activation: invalid signature

The license file is either corrupted in transit or older than the embedded public key expects. Re-request the latest signed file from license@core.at. Don't edit the JSON by hand — any modification invalidates the Ed25519 signature.

8. macOS: “Eldric.pkg cannot be opened — unidentified developer”

macOS Gatekeeper guards against unsigned packages. Eldric 5.0 PKGs are not Apple-notarized (notarized releases are planned for 5.1). To bypass:

• Right-click Eldric-latest.pkg in Finder.
• Choose Open from the context menu.
• Confirm with Open in the security dialog.

9. Where to get more help.

The platform produces detailed logs that almost always have the answer:

journalctl -u eldric-aios --since today --no-pager

If the logs aren't enough, write to office@eldric.ai. Paid-tier customers reach support@eldric.ai with their license ID for prioritised handling.