Install FreePBX 17 on Debian 12

Prepare a clean host

Use a new Debian 12 host or VM dedicated to the PBX. Confirm architecture and current requirements against the official installation guide. The download page gives a starting minimum of 2 GB RAM and 20 GB disk; these are installation minima, not a production sizing promise.

Before installation, establish a restricted administrative network path, reliable name resolution and time synchronization. Save the host's initial configuration. Do not use the installer as an in-place conversion of an unrelated production web server.

Keep Debian stable and the FreePBX platform boundary separate

The FreePBX download page reviewed October 8, 2026 still directs a shell-script installation to a Debian 12 host or virtual machine, and describes the FreePBX 17 ISO as a Debian 12 wrapper. The official installer repository likewise says the script installs FreePBX 17 on vanilla Debian 12.x. Debian separately lists 13.7 as its current stable release and Debian 12 Bookworm as oldstable.

Those statements govern different layers. Debian 13 being current stable does not make it a supported FreePBX 17 installer target, while FreePBX selecting Debian 12 does not return Bookworm to Debian's regular-support phase. Do not remove the installer's version guard, use a skip-version option or silently substitute Debian 13 merely to make the host look current. Record the exact Debian point release, installer commit, package sources and resulting FreePBX and Asterisk versions.

Plan for the Debian 12 LTS support phase

Debian announced on July 12, 2026 that regular Bookworm support had ended and that its LTS team would provide Debian 12 security support until June 30, 2028. Debian also warns that a few packages are outside Bookworm LTS coverage and points administrators to the debian-security-support package for detection.

Treat that date as an operating-system maintenance boundary, not a FreePBX end-of-life date or a guarantee for every installed package, Sangoma repository, commercial module, PHP component, Asterisk build or third-party integration. Inventory the full package and module set, subscribe to the relevant security notices, preserve tested backups and define who will approve a future platform transition. Do not perform an in-place Debian major upgrade on a production PBX without an explicitly supported FreePBX path, isolated rehearsal and rollback.

Follow the official installation path

FreePBX provides a Debian installation script and an ISO path that wraps Debian setup and the installation process. Obtain the script from the official FreePBX repository, read its current instructions and inspect the script before granting root privileges.

Record the exact script revision and options you execute. Follow its supported engine selection instead of independently substituting an Asterisk package. Keep installer logs and stop to resolve failures; a reachable web page does not prove that every required service installed correctly.

The installer’s --dahdi option is a separate hardware decision. Sangoma says the default path does not install DAHDI/Wanpipe drivers and the supported kernel matters for cards. Do not use --testing, --noasterisk or --skipversion as routine production shortcuts; inspect the current documented effect before choosing an exception.

Complete the administration setup

Connect to the intended host using the restricted management path and finish initial administrator setup. Use a unique strong administrative secret. Configure platform identity, time and update settings according to the installed modules. Review any certificate or browser trust issue before transmitting credentials.

Do not publish the management interface to the entire internet to make setup convenient. User access, carrier signaling and media need separate network policies.

Validate an internal first call

Create two PJSIP extensions, apply configuration and register test phones on the restricted network. Test calling in both directions, audio and hangup. Configure off-host backup storage and confirm a successful backup before adding trunks or real numbers. Record actual versions and results; this documentation-based guide does not claim an executed FreePBX installation.

Before migrating a prior major version, follow the separate 16-to-17 migration plan; a fresh installation and a cross-version restore have different acceptance checks.

Prove first web administration after the installer

After preserving the installer log, use the initial-setup guide and Admin login diagnostic to separate completed installation, first administrator creation and authorized module access.