Two of our PBXs are running with expired module licenses (waiting on budget cycle, long story).
While doing updates, one of them upgraded a module past the version we are licensed up to, which of course set off all the new alarms about the module running in an unlicensed state. - no problem with that, but I am wanting to know why is the PBX being allowed to install module versions that it’s not licensed for?? Yes, the repo is/has always been set to mirror.freepbx.org
I just downgraded the one module back down to the version that is approved for our deployment and it seems to have stopped complaining and also no longer shows the newer version as available when I check for upgrades…
Not entirely sure on exact dates but I would say it has probably been 2 months since module updates were last ran so definitely was a bit behind.
Not really a breaking issue as I was able to downgrade back to what we are allowed but more just curious how it could have happened in the first place as I my understanding of how the updates/licenses works was “it shouldn’t”
That fits in to the timeline of when many of these changes were announced and activated. But this does sound like a potential issue in the ordering of some particular module updates. Thank you for the feedback. (Also curious what modules this happened with…)
That may introduce other errors, like security issues and dependency problems, and generally make it more difficult to support these systems in the future because of the inability to anticipatorily reproduce such environments.
Qxact reports. My license says I can be on 17.0.3.10 but was able to go up to 17.0.3.20, at which point I got the warning email and dashboard alerts (working as expected!) - downgraded and back to normal.
Wait, I was told this behavior in the code was stopped “years ago” and got the usual, “You did something wrong” response. I knew that was nonsense, and here’s another instance of FreePBX recently doing something devs claim was coded out long ago.
Not sure if you saw that part @FreerPBXer but IIRC that is different than your situation – you were switching mirrors, correct ?
You aren’t alone there – several folks reported running into issues with unmaintained/insecure third-party mirrors, as you can see in the multiple link-backs at the bottom of the first post of the Avoid walking the plank with expired modules topic. But, generally, once they switch back to the official Sangoma FreePBX mirror, and update/renew support and/or module licenses, then further upgrades on supported versions – 16 and 17 at time of this writing – seem to be fine.
Anyhow, OP’s issue sounds different, and thus far, unique, which may indicate an issue with the specific module at hand.
…[something clearly not in the official Sangoma FreePBX mirror.]
Yeeting some log output into our pastebin could really help e.g. please run fwconsole ma list on the affected system(s).
Also to help clarify, would you mind sharing/confirming:
You were running some commercial modules that you had not renewed maintenance on, but you were content with the older versions ?
And when you ran updates last year, for example, those modules stayed at those previous versions ?
Then this year, with no additional purchase or other major change, such as moving from FreePBX 16 to 17, you started getting automatic updates for those older commercial modules to the latest versions that you were not entitled to ?
Such experience would run counter to the current expected behaviour following the updates over the past few months as outlined in the previously mentioned blog post, and it would also conflict with established procedure from the past ten years as described here (and linked in that other topic):