I recently built a new FreePBX 17 system to replace an older FreePBX 16 system that was built using the custom .iso image. The installation of Debian 12, updates to the OS and then the Github script to download and install FreePBX went really smoothly.
Now that OS updates are handled from Debain, I have patched it from the CLI (sudo apt-get update, sudo apt-get upgrade etc). Yesterday I noticed a couple of updates were held back, one of them being ‘freepbx17’. I took a snapshot of the VM and then proceeded to update the held back packages. This worked, or at least it downloaded and installed the updates, however FreePBX was broken. I tried a couple of things, but didn’t get anywhere, so restored the snapshot.
I’m guessing if I did a clean install, the latest update to freepbx17 would be installed by the script.
Any ideas how we get this update?
Hi @captain_crash The installation script will install the latest freepbx17 package. The freepbx17 package is for to make the initial setup of FreePBX, so it is not recommended to update the freepbx17 package. For this reason, it has been marked as “held.”
hold_packages() {
if [ ! $nofpbx ] ; then
apt-mark hold freepbx17
fi
I think that re-running that package on an existing server overwrites /etc/asterisk/manager.conf and that is why FPBX gets borked. Probably needs to be made more idiot proof because it’s an easy mistake to make. Maybe it could check if manager.conf already exists and show a warning or create a backup before overwriting.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.