Install Script Broken?

koreyb · November 14, 2025, 2:34am

Hi there,

Hoping someone else has had the same issues I’m having currently.

I have now tried 2X to do a fresh install, using the manual install of Debian 12, and the freepbx 17 install script outlined on the website, using all the steps in instructions.

Every time the install script errors out and stops before finishing.

Here’s a snip from the install log. I have the full log available. Is anyone else experiencing this? I’m at al loss because I have installed freepbx17 on another system (same hardware) and had ZERO issues.

"
2025-11-13 20:48:27 - Reloading and restarting FreePBX 17
Reload Started

In Reload.class.php line 859:

Unable to connect to Asterisk Manager

reload [–json] [–dry-run] [–skip-registry-checks] [–dont-reload-asterisk]

2025-11-13 20:48:29 - ****** INSTALLATION FAILED *****
2025-11-13 20:48:29 - Error at line: 1310 exiting with code 1 (last command was: fwconsole reload >> “$log”)
2025-11-13 20:48:29 - Exiting script

pramarajan · November 14, 2025, 4:04am

HI @koreyb It looks like Asterisk is not running on your system. Start Asterisk first, and then try restarting or reloading FreePBX.

koreyb · November 14, 2025, 4:41am

there is for sure more to the story. The install script normally installs everything including asterisk correctly.

When I run asterisk -rv from ssh:

“Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)”

I also noticed the web gui does not work for freepbx and the default site is working for Apache2 on port 80.

I have wiped clean the hard drives and reinstalled 2X now, with the exact results. It makes me believe the install script for freepbx is no longer working correctly OR something has changed in how asterisk/freepbx is installed that the script hasn’t been updated to accommodate.

A few months ago everything installed perfectly without fail.

pramarajan · November 14, 2025, 5:54am

Hi @koreyb Try running Asterisk in the foreground using asterisk -vvvvvvvc and share the output or any errors you see.

kierknoby · November 14, 2025, 5:57am

Hi @koreyb, try using IN1CLICK with a fresh install of Debian 12.

github.com/20telecom/IN1CLICK

freepbx17-on-debian12_README.md

main

# IN1CLICK — FreePBX 17 on Debian 12 [1.0.1]

# Version Update

From 1.0.0 to 1.0.1 on 15th August 2025 16:15 BST by kierknoby

Added "Operating System Check 2" to ensure system is still Debian 12 (bookworm) after update/upgrade and before proceeding. This is now freepbx17-on-debian12 [1.0.1].

---

## Overview

**IN1CLICK** is a streamlined, automated installer script for setting up FreePBX 17 on Debian 12. Developed by 20tele.com, the script simplifies the process by automating all necessary checks, system preparation, package installation, and post-install tasks. It also removes itself on completion, leaving no trace behind.

---

## Disclaimer

The bash script was first published to install FreePBX 17 on 5th August 2025. Contents are provided as-is without warranty of any kind, express or implied. You may modify, distribute, and use this script; 20tele.com accepts no responsibility for any damage or issues arising from its use.

This file has been truncated. show original

It should install everything smoothly. If not, it might then give clues for what’s going wrong.

Kieran

koreyb · November 18, 2025, 1:32am

Hi @kierknoby I gave IN1CLICK a try, and it still fails out. I’m left more confused. Perhaps you can spread some light.

Here are the details:

2025-11-17 19:48:16 - Installation failed at step Reloading and restarting FreeP BX 17. Please check log /var/log/pbx/freepbx17-install-2025.11.17-19.27.02.log f or details.

2025-11-17 19:48:16 - Displaying last 10 lines from the log file

In Reload.class.php line 859:

Unable to connect to Asterisk Manager

reload [–json] [–dry-run] [–skip-registry-checks] [–dont-reload-asterisk]

2025-11-17 19:48:16 - ****** INSTALLATION FAILED *****

2025-11-17 19:48:16 - Error at line: 1310 exiting with code 1 (last command was: fwconsole reload >> “$log”)

2025-11-17 19:48:17 - Exiting script

WARNING: The official FreePBX 17 installation script failed. This isn’t an IN1CL ICK error.

Everything was going OK, until we ran into a problem installing FreePBX 17 or As terisk 22.

What might have happened:

A package failed to install (e.g. a missing dependency or outdated repositor y).
Asterisk did not start properly due to broken modules or invalid configurati on.
If the GUI is broken, Apache may have failed or PHP configuration is incorre ct.

WARNING: The script exited unexpectedly before completing the installation. What you can do now:

Check the FreePBX install logs:

cat /var/log/pbx/freepbx-*.log
Check if Asterisk is running:

systemctl status asterisk
Check for install-time errors:

tail -n 100 /var/log/asterisk/full
Try restarting the FreePBX framework:

fwconsole restart
Use WinSCP (Windows): File protocol: SCP, Host name: enter your IP address, Port: 22, login, go to:

/var/log/pbx/freepbx-*.log

If you need help, email the log to [email protected] or open a ticket at http s://support.20tele.com

IN1CLICK is now exiting due to a failed FreePBX install. Goodbye.

tail -n 100 /var/log/asterisk/full

[2025-11-17 19:42:05] Asterisk 22.6.0 built by jenkins @ 0ea5ef11b0b7 on a x86_64 running Linux on 2025-11-03 07:19:51 UTC
[2025-11-17 19:42:05] NOTICE[117391] loader.c: 367 modules will be loaded.
[2025-11-17 19:42:06] WARNING[117391] res_odbc.c: res_odbc: Error SQLConnect=-1 errno=1045 [unixODBC][ma-3.1.15]Access denied for user ‘freepbxuser’@‘localhost’ (using password: YES)
[2025-11-17 19:42:06] NOTICE[117391] res_odbc.c: Registered ODBC class ‘asteriskcdrdb’ dsn->[MySQL-asteriskcdrdb]
[2025-11-17 19:42:06] NOTICE[117391] cdr.c: CDR simple logging enabled.
[2025-11-17 19:42:06] WARNING[117391] res_odbc.c: res_odbc: Error SQLConnect=-1 errno=1045 [unixODBC][ma-3.1.15]Access denied for user ‘freepbxuser’@‘localhost’ (using password: YES)
[2025-11-17 19:42:06] WARNING[117391] cdr_adaptive_odbc.c: No such connection ‘asteriskcdrdb’ in the ‘asteriskcdrdb’ section of cdr_adaptive_odbc.conf. Check res_odbc.conf.
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of ‘_.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 127 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 128 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 129 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 130 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 131 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 132 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘_X.’ instead at line 133 of extensions.conf
[2025-11-17 19:42:06] WARNING[117391] pbx.c: Context ‘from-did-direct’ tries to include nonexistent context ‘ext-findmefollow’
[2025-11-17 19:42:06] WARNING[117391] pbx.c: Context ‘from-internal-xfer’ tries to include nonexistent context ‘from-internal-custom’
[2025-11-17 19:42:06] WARNING[117391] pbx.c: Context ‘from-internal-noxfer’ tries to include nonexistent context ‘from-internal-noxfer-custom’
[2025-11-17 19:42:06] WARNING[117391] pbx.c: Context ‘from-internal’ tries to include nonexistent context ‘bad-number’
[2025-11-17 19:42:06] WARNING[117391] pbx.c: Context ‘from-pstn’ tries to include nonexistent context ‘from-pstn-custom’
[2025-11-17 19:42:06] WARNING[117391] pbx.c: Context ‘from-analog’ tries to include nonexistent context ‘from-dahdi’
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database user found, using ‘asterisk’ as default.
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database password found, using ‘asterisk’ as default.
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database host found, using localhost via socket.
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database name found, using ‘asterisk’ as default.
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database port found, using 3306 as default.
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database socket found, using ‘/var/run/mysqld/mysqld.sock’ as default.
[2025-11-17 19:42:06] WARNING[117391] res_config_mysql.c: MySQL RealTime: No database socket found (and unable to detect a suitable path).
[2025-11-17 19:42:06] NOTICE[117391] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[2025-11-17 19:42:06] NOTICE[117391] indications.c: Default country for indication tones: us
[2025-11-17 19:42:06] NOTICE[117391] indications.c: Setting default indication country to ‘us’
[2025-11-17 19:42:06] WARNING[117391] xmldoc.c: Couldn’t find manager PJSIPCallIDToChannel in XML documentation If this module was recently built, run ‘xmldoc reload’ to refresh documentation
[2025-11-17 19:42:06] WARNING[117391] xmldoc.c: Couldn’t find manager PJSIPCallIDToChannel in XML documentation If this module was recently built, run ‘xmldoc reload’ to refresh documentation
[2025-11-17 19:42:06] WARNING[117391] xmldoc.c: Couldn’t find manager MessageSendInfo in XML documentation If this module was recently built, run ‘xmldoc reload’ to refresh documentation
[2025-11-17 19:42:06] WARNING[117391] xmldoc.c: Couldn’t find manager MessageSendInfo in XML documentation If this module was recently built, run ‘xmldoc reload’ to refresh documentation
[2025-11-17 19:42:06] NOTICE[117391] res_stir_shaken/crypto_utils.c: Registered object TNAuthList as NID 1248
[2025-11-17 19:42:06] WARNING[117391] res_stir_shaken/verification_config.c: Stir/Shaken verification service disabled. Either there were errors in the ‘verification’ object in stir_shaken.conf or it was missing altogether.
[2025-11-17 19:42:06] WARNING[117391] res_stir_shaken/attestation_config.c: Stir/Shaken attestation service disabled. Either there were errors in the ‘attestation’ object in stir_shaken.conf or it was missing altogether.
[2025-11-17 19:42:06] NOTICE[117391] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.

koreyb · November 18, 2025, 3:37am

On the same system… for interest sake I’ve tried installing using the freepbx 17 ISO.. It get stuck on a install loop… rebooting after failing and trying to install again over and over.

It seems something may have changed with Asterisk or something that the installers have not been updated to accommodate perhaps? I would love to hear if anyone else who is doing fresh installs are having these issues..

kierknoby · November 18, 2025, 8:57pm

It suggests something is/was wrong with the FreePBX installation script itself. We saw an issue like this a while back, hence the IN1CLICK output advising that it can’t complete and possible reasons why. Assume all good up until then. Unfortunately, I’m now getting a 404 from GitHub when trying to run the installation script today to test for you, which is probably related to the Cloudflare aka everyone outage.

koreyb · November 19, 2025, 6:31am

this is what my feeling is as well.. i found the old post from a bit ago… there was a suggestion to try going back to Asterisk 21 and 20… i tried 21, with no luck as the posted version i think was updated since which may have also broken the install script. I do have an issue open and have some engagement directly with Astrisk and sangoma’s team it seems… Given them access to my server to see the install fresh from the OS install, in hopes they can see what’s perhaps causing this. My hope is they find the issue and can correct the problem… No one should have to jump through manual hoops when the steps are in place to make the install straight forward… Fingers crossed.

kierknoby · November 19, 2025, 11:37am

I’ve tested IN1CLICK this morning and it’s working perfectly on a fresh Debian 12 installation.

wget https://raw.githubusercontent.com/20telecom/IN1CLICK/main/freepbx17-on-debian12 -O /tmp/IN1CLICK && chmod +x /tmp/IN1CLICK && /tmp/IN1CLICK

Whatever issue you were experiencing before is either yours alone if it persists or it was relating to the FreePBX script itself, and that has been resolved their end as it’s working for me. Yesterday’s 404 is unrelated.

koreyb · November 19, 2025, 2:02pm

Well.. that’s interesting. I’m guessing the web gui also is working too?

I’m hoping the outage is all it took but seems too simple lol

kierknoby · November 19, 2025, 2:16pm

Yes I was able to access the GUI, no issues.