The installer is designed not to leave you stranded: if something fails it tells you the
exact phase, leaves a diagnostic bundle at /root/nexia-diagnostic.tgz and sends us
an automatic report (no secrets) so we can help. These are the most common snags and their fix.
Golden rule: run it again
The installer is idempotent: completed phases are not repeated. Most failures are transient (a down mirror, a network timeout). The first step is always:
sudo bash install.shConcrete cases
“Signature verification failed”
The downloaded package does not verify against the pinned key. Almost always a corrupt download: delete it and fetch again. If it persists, do not install and write to us — it is exactly what the verification exists to prevent.
The system goes “quiet” for several minutes
Normal during the FreeSWITCH compile (25–40 min on small servers) — since v1.0.1 the spinner
shows the seconds ticking. You can watch the detail in another terminal:
tail -f /var/log/nexia-install.log
“Port conflicts” at preflight
There is other SIP software or a prior web panel (Asterisk, FreePBX, a foreign nginx). NEXIA requires a clean server: reinstall the OS from your provider and start fresh.
It failed at an intermediate phase and the re-run does not skip it
That is expected: the failed phase is retried in full (only completed ones are skipped). If the cause persists, check the last log lines the error itself showed you.
The panel does not load over HTTPS
An IP certificate lasts ~6 days by Let's Encrypt design and renews itself every 6 hours
(systemctl list-timers nexia-cert-renew). If the server was off for several days,
give it a few minutes after powering on or force it:
systemctl start nexia-cert-renew
If you are still stuck
/root/nexia-diagnostic.tgz (it holds the log and phase state; never secrets). We
answer, and the cause is fixed for everyone in the next release.