@BlazeStudios Tom, the recommended way at the point when I did the installations. Clean, virgin Debian 12 and then using the official Sangoma install script. That’s it.
The (beta) install ISO wasn’t recommended at this time.
issue 883 you are not only one seeing this, its been mentioned on irc and newsgroups too, I found this on github
Is the package marked as held or not? That’s the issue, the freepbx17 package needs to be marked as held, if it’s not you get the issue that is happening.
If the package is not marked as held, then run apt-mark hold freepbx17 and that should fix this problem for you.
It initially was not marked on all server by the install script, I’ve manually put it on hold. I already wrote that 6 days ago 
When were these systems installed and what version of the install script were you using?
My bad I thought you were referring to something else.
The first pretty close after FPBX 17 went stable. The other two around 4 months ago. All with the official Sangoma install scripts on a virgin Debian 12.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.