Unable to login post upgrade ✏️ on custom third-party non-stock systems (TITLE EDIT BY MOD)

darcey · October 21, 2025, 3:34pm

I have the update notification email enabled with auto-install disabled. When notified of updates, I run fwconsole ma upgradeall. I also check the resulting status in the FreePBX UI. It shows everything up to date.

notorious.dds · October 21, 2025, 4:23pm

@penguinpbx

Nope.

I installed my system as a VM using the .iso from sangoma. It’s pretty vanilla.

Also, all of my modules are up to date (with the exception of ‘framework’ so that I can still actually log in.)

penguinpbx · October 21, 2025, 4:46pm

Full module list would be appreciated e.g. sudo -u asterisk fwconsole ma list

notorious.dds · October 21, 2025, 5:37pm

Here you go.

mickier · October 21, 2025, 6:59pm

I’m running FreePBX 17 “standard” (if there’s such a thing)–about a month ago I installed Debian bookworm and followed the FreePBX steps, then restored a backup from FreePBX15, however, I am using ClearlyIP’s trunking module which re-branded my system as clearlyip

I just upgraded Framework to 17.0.21.2 and still not working - (might be a ClearlyIP issue?)

penguinpbx · October 21, 2025, 10:09pm

Well, your setup is clearly not vanilla anymore:

^^^ B.I.G. CA-VI-TIES !

Your framework output should look more like this:

| framework | 17.0.21 | Enabled | GPLv2+ | Sangoma |

on column “Unknown” != “Sangoma”

Great!

Is anyone able to reproduce this issue on fully updated stock FreePBX from either the official Sangoma shell installer or BETA ISO, without any custom modules or third-party add-ons ?

_{BONUS, if you can: Once updated, please try on v17 with manual install of framework module version 17.0.21.2 via:

sudo -u asterisk fwconsole ma downloadinstall framework --tag=17.0.21.2}

notorious.dds · October 21, 2025, 11:39pm

Well… that didn’t take long to wade right into the pissing contest between Sangoma and ClearlyIP. Not bad given that my total experience with PBX’s (of any kind) is less than 30 days at this point.

At any rate, now that I’ve performed pirouettes in the no-man’s land between Sangoma’s and Clearly’s trenches, I take it that you’re essentially saying “ClearlyIP has modified the framework. So, if there’s an issue, take it up with them”. I can totally understand that position.

That being said, prior to moving forward with my PBX setup, I thought I had done a descent job doing my due dilegence on the different PBX options. However, this Sangoma v. ClearlyIP battle cought me a little by surprise and one that I wish I had better understood earlier than I actually had.

Oh well… such is life when swimming in the mixing waters of open source and commerial softwares.

tonyclewis · October 22, 2025, 12:17am

ClearlyIP fixed this with the branding module yesterday. Sangoma made changes to framework for 16 and 17 systems for SAML and it broke the skinning of the login page. I know of one Sangoma OEM partners that also had problems with framework breaking login so this was not unique to us.

penguinpbx · October 22, 2025, 1:18am

Welcome to the FreePBX Community Forums!

It is certainly a bit confusing right now in the market and you are not alone in this observation.

Another way to think of it is that Sangoma’s stewarded FreePBX is upstream and there are others that are downstream. Related, one take-away for those downstream from the GIT commit a month before OP – that was dramatically referenced earlier in this topic – might be:

When there’s logs upstream
Should you row hard to change course
Or just ignore them ?

reconwireless · October 22, 2025, 1:36am

Can you please explain what you trying to say here?

jeffreythebuilder · October 22, 2025, 2:09am

Yes,
Using Sangoma hardware with original firmware on PBXAct 16, and on ~~updated BETA ISO PBXAct 17~~ Debian 12 installation method will face this issue as well.

Edit: I am unable to reproduce this on limited customers we have on PBXAct 17 Beta ISO right now.

darcey · October 22, 2025, 7:56am

@penguinpbx My install, whilst ‘custom’ to some extent has no third party or extraneous mods. It should present a good platform on which to determine the cause of the bug
Also AFAICT it does appear to be up-to-date (other than for framework ATM).

penguinpbx · October 22, 2025, 4:48pm

That could be fun, but, this module went through a lot of internal testing, and we aren’t seeing issues with fully updated stock systems. ~~Therefore, the latest versions are now back in the official mirrors.~~ EDIT: Back to holding again at 17.0.21 to help downstream.

Slightly aside, there is a similar – but probably unrelated – issue at [bug]: Insecure connection password warning in Firefox hides Continue and Cancel buttons · Issue #896 · FreePBX/issue-tracker · GitHub that you might be interested in following.

darcey · October 22, 2025, 5:08pm

Thanks. I had come across that. It looks to me like the user simply needs to move focus away from the password field in order to suppress the popup & reveal the buttons. That’s just standard firefox behaviour AIUI.

FreerPBXer · October 23, 2025, 10:18pm

I’m curious how something this widespread got through testing. Can you explain?

penguinpbx · October 24, 2025, 1:16am

Are you able to share any related problem reports regarding stock FreePBX systems (from either the Sangoma shell installer or BETA ISO) ? Not seeing any in this topic so far :-/

Or does this look to you more like a downstream (automated ?) repackaging issue of framework affecting MustardmanPBX and the like ?

If the latter, then are you curious about the QA testing by downstream into the upstream changes (previously linked) made in the open source GitHub repository one month before Sangoma began shipping framework version 17.0.21.2 ?

darcey · October 27, 2025, 8:48am

Following on from advice above, I have installed an instance of FreePBX in an Proxmox lxc container using the Debian 12 install script.
Is it viable to now hone down the installed modules to get back to something like the system I posted here?
I’d prefer a minimal system, to conserve resources and have a simplified system on which to learn about Asterisk and FreePBX.

BTW is this commit related to the login issue?

mickier · October 27, 2025, 2:50pm

…this issue is resolved for those of us running the clearlyip trunking module (system now upgraded to framework to 17.0.21.2)

GRATEFUL thanks to all who assisted in the solution!

penguinpbx · October 28, 2025, 4:17am

You are very welcome!

However, running downstream third-party “add-on” modules that actually modify framework or other core parts of FreePBX is not supported by Sangoma and may cause other subtle/not-so-subtle issues for such systems in the future. This is especially so for those (re)distributors that do not closely follow upstream code changes in the open source FreePBX GitHub repositories, but who insist on hastily and/or automatically repacking said changes anyhow.

penguinpbx · October 28, 2025, 6:00pm

Maybe ?

The --opensourceonly option of the shell installer is a community member led effort in this direction. (OSO spice of the BETA ISO wraps around it.) But if you don’t like it, then you can probably get back to a more “official” option by running:

$ sudo apt install sysadmin17

…but not tried that myself (would seem easier to redo the install from scratch at that point, using either shell installer or ISO.)

Although, I did take a stab at something like reduced module installation previously to help with some independent module testing/development before v17 shell installer was released (actually it was back before v17 was even a tarball – probably should archive that repo someday.)

That’s a noble goal.

However, there’s been some other “new” projects that completely cannibalize and relabel the FreePBX work as their own, stripping out some modules and modifying others, getting it One Piece at a Time like a JohnnyCashPBX or MusterdmanPBX they come and go when new owners/investors swoop in to jettison everything in the catalog except the customer lists that they use to upsell their own shiny new kitchen sinks to, confusing/stranding a lot of end users along the way due to bit rot from elimination/de-prioritization of open source contributions.

It is definitely in the same ballpark, but it is not the exact issue at hand in your OP. There are multiple new and recent improvements to the login experience in the mix. Please expect more formal announcements about this soon!