The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →FreePBX is a web-based, GPL-licensed management interface for the Asterisk open-source PBX engine. FreePBX 17 can be self-hosted on a virtual private server (VPS), and the documented cloud installation uses a fresh Debian 12 server with at least 2 GB of RAM and 20 GB of disk. You install it with the official Debian script, finish setup in a browser, then secure, back up and maintain the resulting internet-facing phone system.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What FreePBX is
FreePBX is not a phone carrier and it is not a replacement for a SIP trunk. It is the administration layer that lets you configure an Asterisk private branch exchange (PBX) through a browser instead of editing every telephony setting by hand. Asterisk supplies the underlying call-processing engine; FreePBX supplies the modular PHP and JavaScript interface, configuration tools and management workflow.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Grandstream UCM6300A Audio IP PBX | 0 FXO Ports, 0 FXS Ports | Desktop/Wall-Mount | $169.99 | Buy on Amazon |
| 2 |
|
Sangoma FreePBX Phone System 40 | $695.00 | Buy on Amazon |
| 3 |
|
Sangoma Technologies Inc-Sangoma FreePBX System 100 Users | $1,195.00 | Buy on Amazon |
| 4 |
|
Elastix ELX-025B PBX IP VoIP | $1,137.40 | Buy on Amazon |
| 5 |
|
Sangoma FreePBX Phone System 60 | $845.00 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The project describes FreePBX 17 as an open-source, GPL-licensed, Debian-based release. You can use it to manage extensions, inbound and outbound call rules, voicemail, queues, conferences, recordings and other Asterisk features, provided that you also arrange compatible phones, trunks and network connectivity. The FreePBX project repository describes the software as “a completely modular GUI for Asterisk written in PHP and Javascript.”
This separation matters when planning a deployment. FreePBX changes the configuration of Asterisk; it does not supply telephone numbers, minutes, emergency-service coverage or a guaranteed connection to the public telephone network. Those pieces come from your SIP provider, hardware gateway or another telephony service.
#1 Best Overall
- Supports up to 1500 users and up to 200 concurrent calls
- Zero configuration provisioning of Grandstream SIP endpoints
- Built-in Instant Messaging (IM), Audio Conferencing & Web Meetings platform that supports access from computers, mobile devices, and SIP endpoints
- Free Wave App allows easy voice & Instant Messaging (IM) communications using desktops, Web, and Android/ iOS devices
- API available for third-party integrations, including CRM and PMS platforms
FreePBX and Asterisk at a glance
| Component | Role | What you administer |
|---|---|---|
| FreePBX | Web management layer | Users, extensions, routes, modules, permissions and system settings |
| Asterisk | PBX and media engine | Call signaling, dial plans, media handling and telephony services |
| SIP trunk or gateway | Connection to external telephone networks | Provider account, numbers, authentication and carrier-specific requirements |
| VPS | Virtual server hosting the software | Operating system, firewall, storage, snapshots, monitoring and network access |
Can FreePBX 17 run on a VPS?
Yes. The official cloud guidance uses a fresh Debian 12 image and specifies a starting minimum of 2 GB of RAM and 20 GB of disk. These figures are a baseline for getting the system installed, not a universal capacity recommendation. Actual requirements depend on the number of simultaneous calls, call recordings, transcoding, conferencing, voicemail retention, backups and monitoring services.
The documented support target is Debian. Sangoma’s FreePBX FAQ identifies Debian 12 as the supported operating-system line for FreePBX 17 and says the installer uses PHP 8.2.x by default; commercial modules are tested against that PHP line. Ubuntu and other Debian-derived distributions may work in some circumstances, but they are not the official support target described by that FAQ. Choosing Debian 12 avoids starting with an operating system outside the documented path.
Minimum starting point
| Resource | Official cloud baseline | How to interpret it |
|---|---|---|
| Operating system | Debian 12 | Use the provider’s clean Debian 12 image rather than a preconfigured application image. |
| Memory | At least 2 GB RAM | Suitable as an installation starting point; busy systems and media-heavy workloads may need more. |
| Storage | At least 20 GB disk | Leaves room for the base system and application, but recordings and backups can consume it quickly. |
| Access | Root or equivalent administrative access | Required to install packages, services and system-level telephony components. |
| Connectivity | Working network connection and a reachable server | The installer downloads dependencies and you later reach the web interface and SIP services over the network. |
Do not treat the baseline as a promise that every deployment will fit permanently. A system that stores continuous recordings, handles concurrent conferences or keeps local backup copies needs a capacity plan based on retention and usage. The official material does not publish a universal sizing table for those workloads, so measure your own call and storage patterns and leave operational headroom.
Choose a VPS installation route
For a normal cloud server, the script-based installation is the most direct route. FreePBX also publishes a version 17 ISO based on Debian 12, while a dedicated appliance is an option when you need preselected hardware or integrated telephony interfaces.
| Route | Operating-system starting point | Control of host | Best fit | Important trade-off |
|---|---|---|---|---|
| Official Debian script | Provider’s fresh Debian 12 image | High; you manage the VPS operating system and network | Most VPS deployments and administrators comfortable with Linux | You are responsible for hardening, backups, updates and troubleshooting. |
| FreePBX 17 ISO | Debian 12 supplied inside the ISO workflow | Depends on whether the host accepts a custom ISO | Bare metal, virtual machines or providers that support ISO installation | Less convenient when a VPS only offers standard distribution images. |
| Dedicated appliance | Vendor-selected platform | Lower underlying-host control | Sites needing dedicated telephony hardware or a packaged system | Less flexibility than assembling your own VPS and may carry hardware-specific costs. |
The choice is not only about installation speed. Compare snapshot and backup facilities, public-IP controls, firewall capabilities, SIP and NAT behavior, hardware-card requirements, maintenance responsibilities and the level of commercial support you need.
Prepare the VPS before installing
Provision the server before you run any FreePBX command. A clean starting point prevents old PHP packages, web servers or database settings from colliding with the installer.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteRank #2
- Select Debian 12, not an Ubuntu image, if you want to stay within the documented FreePBX 17 support path.
- Allocate at least 2 GB of RAM and 20 GB of disk; increase storage when recordings or local backups will remain on the same machine.
- Record the server’s public address and confirm that your provider allows the network traffic required by your selected SIP trunk and phones.
- Ensure you can connect with root or an equivalent administrative account. The installation changes system packages and services.
- Decide where configuration and recordings will be backed up before putting real users on the system.
- Plan administrative access from a trusted network or VPN instead of exposing the management interface unnecessarily.
Install FreePBX 17 on Debian 12
The official getting-started workflow is a script installation on a fresh Debian 12 cloud image. The installer resolves dependencies and installs the FreePBX components; the guide says the process can take around 30 minutes or longer depending on server speed and internet bandwidth.
- Provision Debian 12. Create a new VPS from the provider’s Debian 12 image. Avoid reusing a server that already hosts another web stack or PHP version.
- Connect administratively. Open a root or equivalent privileged shell using the access method supplied by your VPS provider. Confirm that the server has working network access.
- Obtain the official installer. Download the current
sng_freepbx_debian_install.shscript from the FreePBX installation documentation or its official project repository. Use the copy supplied for FreePBX 17 rather than an older major-release script. - Run the script. Execute the downloaded script in the privileged shell, following the options documented for your installation. If you need DAHDI support for compatible Sangoma digital or analog cards, the installation guide documents the optional
--dahdiargument. - Wait for completion. Leave the session connected while packages, services and FreePBX components are installed. A run taking roughly 30 minutes or more can be normal on a slower VPS or network connection.
- Open the web interface. When the script finishes, browse to the server’s IP address and complete the initial web setup. Create the administrative account and supply the system values requested by the setup screens.
- Test before production use. Sign in, verify that the expected modules and Asterisk services are running, then configure a test extension and controlled call before connecting all users or a production trunk.
What the installer changes
The script is more than a FreePBX web-file upload. It installs the operating-system dependencies, PHP line, web components, database and Asterisk-related services needed by the distribution. That is why it should run on a clean server and why administrative access is required. Do not install a second PHP stack or an unrelated control panel first and expect the same results.
Using the ISO instead
The FreePBX 17 ISO is based on Debian 12 and automates much of the installation. It is useful for a physical server, a virtual machine that accepts custom ISO media or a hosting environment where you control the boot process. A typical managed VPS workflow starts with the provider’s Debian image instead, because many VPS products do not expose virtual CD/DVD or custom-ISO controls.
The ISO documentation says root login through the local or remote command-line terminal is disabled by default for security. Follow the access method created by the ISO and do not assume that the root SSH behavior of a generic Debian server applies to that installation route.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallNetwork, SIP and NAT planning
A VPS PBX is an internet-facing communications service. You need to design both the application and the network path: the VPS public address, any provider firewall, the host firewall, SIP-trunk requirements, phone registration, media traffic and NAT behavior.
There is no single official port list that fits every FreePBX deployment. Required rules vary with the SIP trunk, phone model, transport protocol, NAT design and provider documentation. Start with the exact requirements of your trunk and handsets, permit only the traffic you need, and test inbound signaling, outbound signaling and two-way audio separately. Copying a generic firewall list can expose unnecessary services or still fail to handle media correctly.
Rank #3
- FreePBX up to 100 extensions and 60 concurrent calls
- 2 PCI Express Full Length Slots
- 3 Onboard GIG Network Ports
- Single 250GB SSD drive
- Quad Core Processor, 4 GB of Memory
Practical connectivity checks
- Confirm the VPS has a stable public address and that any cloud security group agrees with the host firewall.
- Restrict the web administration interface to trusted addresses or a VPN whenever your provider and work practices allow it.
- Use the SIP carrier’s documented NAT and registration settings rather than guessing from another provider’s example.
- Place test calls in both directions and verify that audio works on both sides; signaling that succeeds while media fails usually indicates a firewall or NAT problem.
- Keep provider support information, trunk credentials and the intended firewall policy in your operations documentation.
Secure the self-hosted PBX
FreePBX gives you control, but a public VPS also gives attackers a target for password guessing, fraudulent registrations and unauthorized outbound calls. Apply the following controls before inviting users to register phones:
- Use unique, long credentials for the FreePBX administrator, Linux accounts, extensions and SIP trunk.
- Limit administrative web access to trusted networks or a VPN; do not leave the management interface broadly reachable when it is not necessary.
- Enable the VPS provider’s firewall and configure a host firewall with a narrow, documented policy.
- Keep Debian, Asterisk, FreePBX modules and other installed components patched. Schedule maintenance rather than postponing security updates indefinitely.
- Monitor authentication events, extension registrations, call destinations and unusual outbound volume. Unexpected international or premium-rate calls can indicate credential abuse.
- Back up configuration and recordings, and periodically verify that a backup can actually be restored.
- Separate administrative accounts from normal user accounts and remove access that is no longer needed.
Security is an operating process, not a one-time installer setting. Review firewall rules and accounts after every trunk, phone, module or network change.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Plan resources around your workload
The 2 GB/20 GB baseline answers whether a small installation can start; it does not answer how much capacity your organization needs. Use the workload characteristics below to decide what to expand first.
| Workload | Why it changes capacity or operations | Planning response |
|---|---|---|
| More simultaneous calls | Increases Asterisk processing and concurrent network activity. | Measure peak concurrency and leave CPU, memory and network headroom. |
| Call recording | Consumes disk continuously and creates backup data. | Define retention, monitor free space and consider separate backup storage. |
| Transcoding | Converts codecs and can require substantially more CPU than pass-through calls. | Prefer compatible codecs where practical and observe CPU during peak use. |
| Conferencing | Mixes multiple media streams and increases processing and bandwidth. | Test the expected participant count rather than sizing from extension count alone. |
| Local backups and monitoring | Consume storage and add scheduled jobs. | Account for backup generations, logs and monitoring retention separately from the 20 GB starting point. |
Because the official guidance does not provide a universal workload-sizing table, validate your plan with real peak usage and adjust the VPS before memory pressure, disk exhaustion or CPU saturation affects calls.
Backups, updates and daily operations
Back up what the PBX cannot recreate
Protect both configuration and recordings. A configuration-only backup will not restore the business value of stored calls, while a recordings-only copy cannot rebuild extensions, routes and credentials. Keep at least one backup outside the VPS so a provider outage, accidental deletion or compromised server does not destroy every copy.
Patch deliberately
Keep the Debian base system, Asterisk, FreePBX core and installed modules current. Read release notes for compatibility and schedule a maintenance window when updates could restart telephony services. Test a representative inbound call, outbound call, voicemail and recording after maintenance.
Rank #4
- Up to 100 extensions
- Up to 50 concurrent calls
- Voicemail
- Fax-to-email
- Support for softphones
Monitor the service
Watch disk usage, memory, CPU, service availability, failed logins, registration changes and call activity. Recording-heavy systems can fill their disks quietly; authentication monitoring can reveal abuse before a carrier bill does.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Major-version upgrades and migration
Do not assume an older FreePBX major release can be upgraded in place with the normal script or upgrade utility. The FreePBX project warns that upgrades from an older major release require a fresh installation and transfer of data. For a FreePBX 17 migration, build a new supported Debian 12 system, install FreePBX 17 through the documented route, move the required configuration and recordings using a tested backup process, then cut over phones and trunks in a controlled window.
Keep the old system available until test calls, voicemail, recordings and administrative access have been verified on the new server. Document any module or provider-specific settings that cannot be transferred automatically.
Troubleshooting common VPS problems
The installer stops or takes much longer than expected
Installation can take around 30 minutes or more. First check the VPS’s network connection, available disk space and provider console for failed package operations. Do not launch several installer processes at once. If the run fails, capture the final error, correct the underlying package or connectivity issue and follow the official recovery guidance rather than mixing scripts from different FreePBX releases.
The web interface does not open
Confirm that the script completed, the VPS address is correct and both the provider firewall and host firewall allow the web service from your test network. If the service is intentionally restricted, test from the trusted network or VPN you selected for administration.
Phones register but calls have one-way or no audio
This usually points to the interaction between SIP signaling, RTP media, NAT and firewall rules. Recheck the trunk’s documented NAT requirements, the phone network and the cloud firewall. Avoid importing a generic port list; compare each rule with the selected carrier and phone design.
Best Value
Disk usage rises unexpectedly
Check recordings, voicemail, backup generations and logs. Set retention rules, move backups off the PBX where possible and alert before the disk reaches capacity. A 20 GB disk can be consumed quickly by media files even when the initial installation succeeded.
An update breaks a module or phone behavior
Review the module and FreePBX release notes, restore the last known-good backup if necessary and test on a maintenance window. Keep a written inventory of installed modules and provider settings so you can identify what changed.
When a VPS is the right choice
A VPS suits teams that want control over the operating system, public-IP and firewall policy, snapshots and backup design without buying a physical server. It also makes it easy to scale disk or memory as call recordings and concurrency grow. The trade-off is operational responsibility: you must secure the host, understand SIP/NAT behavior, monitor calls and maintain the software.
The ISO or a dedicated appliance can be preferable when you need a controlled boot image, dedicated telephony cards or a packaged support arrangement. Hardware cards are not required for a SIP-only VPS deployment; they become relevant when connecting compatible digital or analog telephony hardware, for which the installer’s optional DAHDI support is documented.
FreePBX 17 VPS checklist
- Fresh Debian 12 image selected.
- At least 2 GB RAM and 20 GB disk allocated, with additional capacity planned for recordings and backups.
- Root or equivalent administrative access confirmed.
- Official FreePBX 17 Debian script obtained.
- Provider firewall and host firewall policy written before production use.
- Administrative web access restricted to trusted networks or a VPN where possible.
- SIP trunk, phones and NAT requirements documented from the selected providers.
- Configuration and recording backups stored separately and restoration tested.
- Monitoring enabled for disk, authentication, registrations and call activity.
- Migration plan prepared if replacing an older major FreePBX release.
Bottom line
FreePBX 17 is the browser-managed control layer for Asterisk, and Debian 12 on a VPS is its documented cloud deployment path. Start with the official 2 GB RAM and 20 GB disk baseline, install on a clean image with sng_freepbx_debian_install.sh, complete setup in the browser, then treat the server like any public communications system: restrict access, tailor firewall and NAT rules to your actual SIP design, back up configuration and recordings, monitor call activity and plan a fresh installation for major-version migrations.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
