Run the preflight and guided installation

Resolve the preflight findings

Run the command below from the extracted kit. This preliminary check, called preflight, asks questions about your FreePBX installation and the choices for your Obelisk setup, such as the database location and account details. Answer using your actual FreePBX settings; the question-by-question guide linked below explains each choice. The check reports missing requirements without installing Obelisk. Resolve the reported errors before continuing. You will enter the answers again when starting the installation. The website and its certificate are checked during installation, not by this command.

cd /root/obelisk-install &&
bash install.sh --check

Complete the guided questions

1. Database and source tables

   Choose local or remote according to where your database is located. Identify the existing database containing CDR and queuelog, usually asteriskcdrdb, then choose the name of the separate Obelisk database. For a local installation, the installer creates the application account. For a remote database, enter the existing application and administrative logins. If you are unsure, open FreePBX → Settings → Advanced Settings. Check whether CDR uses a remote database and note its connection details and database name. Also check any custom name configured for the queue-log database or table: give the installer the database name and the queuelog table name in their respective fields.

2. First administrator, telephone numbers and AMI

   Choose the Obelisk administrator username and password, telephone-number format and automatic-report language. AMI connects Obelisk to Asterisk to show live calls and queue status. Choose an existing AMI account or let the installer create a dedicated account in FreePBX’s /etc/asterisk/manager_custom.conf. A new account needs the FreePBX configuration reload offered at the end of installation. The PBX administrator can later change or remove this account; if the credentials change, enter the new ones in Obelisk → Administration → System and utilities → Asterisk and databases, using the guide below. Removing the account stops this connection until you configure a valid replacement. If the installer generates your web-login password, copy and save it when shown.

3. Review before confirming

   Enter the address you use to open FreePBX, without /obelisk. HTTPS and HTTP are both allowed, including a private IP address. If you use HTTP or an invalid or self-signed HTTPS certificate, the setup explains the issue and asks whether to continue: answer y to accept, or n to stop. Review the installation summary before confirming. The setup still checks that private files cannot be opened from the browser.

bash install.sh

Finish or resume the same installation

A successful installation reports its result and schedules Obelisk jobs. It also requests activation of its two SQL events, min_queue and min_out. These are tasks scheduled by MariaDB or MySQL that process queue and outbound-call data to populate Obelisk’s call reports. Other automatic tasks, such as collecting live data and sending reports, use the scheduled Obelisk jobs. Resolve any activation warnings before relying on automatically updated data. If you defer the FreePBX reload, apply the configuration before testing live views; that reload can also apply other pending FreePBX changes. A PBX reboot is not required. If installation stops and reports saved recovery state, retain its log and run the following command from the same kit.

bash install.sh --resume

If the website or certificate check fails

For an invalid certificate, you decide whether to accept it: for example, a self-signed certificate or one that does not match a private IP address. The same applies if you choose HTTP. Read the warning and answer y to continue, or n to stop; pressing Enter means no. This choice applies to the installer check. A site that cannot be reached, or private files that are accessible, must still be corrected.

1. Test the configured hostname

   If the setup cannot reach FreePBX, check the address from the PBX itself. Opening it from your computer may work while the PBX is unable to reach it. This optional command checks the connection; replace the example address with your own. If the error concerns only the certificate, use the choice offered by the installer.

   Command

   curl --noproxy '*' --connect-timeout 5 --max-time 15 -I 'https://pbx.example.com/'

2. Correct the address and resume

   If you entered the wrong address and setup stopped at the web check, you can correct it with the command below. Replace the example address with your own and run it from the same installation kit. This option applies before installation changes begin; it does not change the address of an already installed application. The setup will ask again whether to accept HTTP or an invalid certificate.

   Command

   bash install.sh --resume --base-url=http://192.168.1.10