Early on 2026-06-01T06:00:00Z, Sangoma Ops teams will be powering down some legacy FreePBX software package delivery infrastructure that is no longer in use by currently supported versions of FreePBX. These updates are necessary to continue to provide secure package delivery services to the community and will help us reach our goal of modernizing our backend systems. This work does not impact v16 or v17 installations. However, admins (not users) of earlier EOL’d versions may wish to review their systems and their Sangoma portal accounts (if any) and are encouraged to take backups in preparation for upgrades to modern supported architectures like FreePBX 17 (link to download instructions.)
Good questions, thanks. We are talking about some really, really old infra – like kickstarter and CentOS 6 stuff! These are things that have long been EOL’d.
Reviewing portal.sangoma.com might be helpful for MSPs/VSPs who are managing multiple FreePBX deployments for their customers as it offers a way to look through their systems to determine which ones still need to be updated to FreePBX 17, double-check any commercial license renewals, etc.
To be clear, we are not changing anything, we are simply powering down some things. If that goes well, then eventually we’ll recycle the bits into new goods and wonderful services.
It would have been helpful if you had answered either of the questions posed by @BlazeStudios and @billsimon . Please provide detail regarding the affected versions, regardless of whether they are EOL. I can see that you tagged v15 in the topic, but you claim it’s only older CentOS 6. Providing clarification is something that someone in your position should be doing.
Are you noticing any issues following the power-off ? That’s the #1 question here. EOL notifications should/did go out years (decade ?) ago for all of these things that were powered off this morning. But good eye on the v15 tag – really that was more of a nudge for folks to upgrade to v17 ASAP and covers the extremely unlikely edge case of somebody using a hybrid CentOS 6/7 RPM system.
Logs were analyzed internally in detail and the affected servers were determined to no longer be in use. Anyone who was running long EOL’d software was (potentially) already operating in a broken state. Should any such admins/users look around and find this topic, then that is a good thing because they may have a (leftover) server that they did not know about – potentially this notification and underlying decision helps those in the vanishingly small number of edge or dusty corner cases to dramatically improve their security posture.
Howdy @adell4444 - While I agree that this may not sound like the greatest policy. Please rest assured that there was deep discovery spanning multiple teams. At the end of the day, couple this with the EOL facts, zero issues reported at forum, or with support tickets- and this is what it is… transparency.
@mwhite Two longtime contributors to the project asked direct, reasonable questions: which versions are affected, what specifically should we check in our portal accounts, and why was this a midday-Friday notice? These questions still haven’t been answered.
Transparency is answering questions directly - you can’t just claim it on the basis that no forum posts or tickets have surfaced issues. That’s absence of evidence, not evidence of absence, especially given the late notice window and the vagueness of who’s affected. EOL or not: what specifically is the infrastructure that was powered off?
Affected versions are old EOL versions before v15 (as already mentioned – but there might be a few hybridized v15’s out there running older packages…)
Users of portal.sangoma.com should consider checking their accounts for older EOL systems that they need to update to v17 (as mentioned in earlier reply.)
This midday-Friday notice was an additional courtesy notification for members of the FreePBX community (that followed previous EOL notices sent many moons ago.)
Curious @adell4444 if you have some forum topic references to situations like this in the past where additional post-EOL notifications were distributed ?
The specific infrastructure that was powered off is mostly some old packaging and kickstarter servers (and their mirrors) from long ago EOL versions (as posted about above.)
Minor update
Not all of the systems were powered down yet – a few more will be shut down later this week around 2026-06-03T06:00:00Z.
@penguinpbx This is the detail that was missing, and it’s the answer the thread needed. Thanks for laying it out clearly.
No, I don’t have references to prior post-EOL courtesy notices, and that’s sort of the point. A courtesy notice is a good thing to do, which is exactly why the specifics belonged in the original notice rather than coming out over several days of back-and-forth. At least they’re on record now, so anyone who stumbles on this thread later is better off for it.
And thanks for mentioning the June 3 shutdowns. That’s the useful bit for anyone still reading, since the first notice didn’t cover the whole decom.
on the 