Fresh Install Already Patched for Debian 13 Upgrade Lock

azon2111 · March 27, 2026, 4:24pm

Does anyone know if the v17 install script was updated to address the blocking of the auto upgrade to Debian 13 OS or if we still need to do that separately?

Thank You.

penguinpbx · March 27, 2026, 4:44pm

It was fixed about 6-7 months ago, yes:

Github issue #197 - Adding below improvements · FreePBX/sng_freepbx_debian_install@d0a045c · GitHub
Adding "--disable-deb-update-v13" CLI option to disable the existing · FreePBX/sng_freepbx_debian_install@7d938b3 · GitHub
Merge pull request #190 from AndrewPaglusch/pin_debian_12 · FreePBX/sng_freepbx_debian_install@723a70b · GitHub

Are you seeing any issues at this time ?

MAWalker · April 1, 2026, 2:13pm

I’ve personally avoided moving any deployments from v16 previously because of initial installation & then subsequent Debian upgrade problems I’ve seen on the forums previously (also, I typically use PBXact, which I don’t believe was live in v17 in the earlier days), however, I want to try v17 at some point soon if the initial installation process & subsequently running system is reliable & stable without to much v17 specific faffing about with failed installation components/settings etc.

So just to be clear, if I perform a fresh install of Debian v12.13 (as described on https://sangomakb.atlassian.net/wiki/spaces/FP/pages/295403538/FreePBX+Open+Source+-+Step+By+Step+Debian+12+Installation), then download & run the FreePBX17 setup script (sng_freepbx_debian_install.sh) for the 1st time (as described on https://sangomakb.atlassian.net/wiki/spaces/FP/pages/230326391/FreePBX+Open+Source+-+FreePBX+17+Installation), this is likely to install successfully & work out-the-box (so to speak) -AND- there’s NO LONGER any additional work required to prevent Debian from upgrading to v13 & breaking FreePBX17 down the line. Is that correct ?

azon2111 · April 2, 2026, 1:03pm

I too am trying to determine this exact scenario. We see the fixes but doesn’t really clearly state that fresh v17d12 deployments are also covered. Maybe it is implied but we are also wanting confirmation as well. @penguinpbx is this correct?

billsimon · April 2, 2026, 2:55pm

github.com/FreePBX/sng_freepbx_debian_install

sng_freepbx_debian_install.sh

master


      
          block_debian13_trixie_update() {
          	cat >/etc/apt/preferences.d/99-block-trixie.pref <<'EOF'
          # Block Debian 13 Trixie
          Package: *
          Pin: release n=trixie
          Pin-Priority: -1
          
          EOF
          }
          
          fix_debian12_repo() {
          
          	# --- Fix sources.list files to use bookworm ---
          	for file in /etc/apt/sources.list /etc/apt/sources.list.d/*.list; do
          		[ -f "$file" ] || continue
          		# Replace "stable" with "bookworm"
          		if grep -qE "deb\s+$DEBIAN_MIRROR\s+stable\b" "$file"; then
          			sed -i.bak -E "s|(deb\s+$DEBIAN_MIRROR\s+)stable\b|\1bookworm|g" "$file"
          		fi

This file has been truncated. show original

penguinpbx · April 2, 2026, 3:44pm

Yes, please try it @azon2111 – unable to reproduce this issue for at least six months now on new installs. Also, rather partial to the latest v17 ISO

azon2111 · April 2, 2026, 3:49pm

Thanks for this, just wanted to confirm for peace of mind, still traumatized over the d13 upgraded PBX which we had to patch back together.

azon2111 · April 2, 2026, 3:49pm

Thanks for this, just wanted to confirm for peace of mind, still traumatized over the d13 upgraded PBX which we had to patch back together.Thanks for this, just wanted to confirm for peace of mind, still traumatized over the d13 upgraded PBX which we had to patch back together.