Back up currently installed versions of modules, Restoration?

I have been trying to fix an intermittent issue and having little luck. Found today that there are updates to several modules available. Frankly, I’ve been afraid to upgrade because the system works as it is and there are many threads about modules getting shut off if you don’t throw money at Sangoma. (Management has forbidden this because of what happened when the phone system was sold to us.)

I’ve found several threads asking about how to install a specific version of a module, but no answers or examples. Other than doing a full bitwise backup of the SSD in the system to have something to fall back on, is there any way for me to back up the currently installed versions of the modules on the system? If so, how would I go about reinstalling them if I were to upgrade and either run into something major being broken or find out that I’ve ‘walked the plank’ out of ignorance? I would rather not rely on the old versions being available to install from the online repository if I can help it.

As discussed in that blog post, you can check your license status for commercial modules at portal.sangoma.com – also please share the output of:

fwconsole setting MODULE_REPO

[http://mirror1.freepbx.org,http://mirror2.freepbx.org]

If you’ve maintained those official Sangoma-provided mirrors for all FreePBX module downloads, and your review of any commercial licenses in the Sangoma Portal site shows they are still currently receiving maintenance support, then assuming you are on a supported v16 or v17 system you should be fine to update and encouraged to do so for security and compatibility reasons as well as new feature support.

As mentioned in the linked threads, this system is on version 13. We haven’t kept up on maintenance due to Sangoma choosing not to fix the firewall problem I discovered 2 weeks after the system was delivered because 13 ‘was being sunsetted’… this was after Sangoma sold us several thousands of dollars of extra software / hardware that were locked on v13. There were also other misleading things told me, which resulted in my having to do an order of magnitude more work than was presented during the sales process; support basically said “you’re on your own” for these tasks. I figured them out & made it work, but it delayed implementation for 3+ months while I figured out how to back-door building the phone configs, something I should never have had to do. Based on everything, I honestly don’t blame management for saying ‘no more’, plus I as IT don’t really want to lose the HA feature. After I got the system functioning, I upgraded NOTHING as one upgrade done when the PBX was on my bench made me have to start over. (This is why I put in my original request “run into something major being broken” as a possible reason to want to revert to the presently-installed versions.)

Back to the point of this thread: is there any way for me to back up the currently installed versions of the modules on the system? I found a thread from 2022 that says someone on the trixbox forum helped the thread creator out, but I’d rather not poke him about something that happened 4 years ago if possible.

Yes, you run a backup of the system. Tell it to backup all the modules and there you go. When you restore, you are restored to that backup.

Thanks Tom

You can also check the module cache directory for module tarballs, for me it’s /var/www/html/admin/modules/_cache/, might be different on distro, Debian, etc. I don’t think there’s any automated cleanup process so likely you’ve got a bunch of versions to choose from.

root@pbx:~ $ ls -lah /var/www/html/admin/modules/_cache/
total 741M
drwxrwxr-x.  3 asterisk asterisk  16K Sep  5 16:15 .
drwxrwxr-x. 50 asterisk asterisk 4.0K Sep  5 16:15 ..
-rw-rw-r--.  1 asterisk asterisk  12K Dec  8  2022 accountcodepreserve-16.0.0.1.tgz.gpg
-rw-rw-r--   1 asterisk asterisk  12K Jul 23  2024 accountcodepreserve-17.0.0.1.tgz.gpg
-rw-rw-r--   1 asterisk asterisk  12K Apr  1  2025 accountcodepreserve-17.0.0.2.tgz.gpg
-rw-rw-r--.  1 asterisk asterisk  71K Dec  8  2022 announcement-16.0.6.tgz.gpg
-rw-rw-r--   1 asterisk asterisk  71K Jan 22  2024 announcement-17.0.1.tgz.gpg
-rw-rw-r--   1 asterisk asterisk  71K Jul 23  2024 announcement-17.0.2.1.tgz.gpg
-rw-rw-r--   1 asterisk asterisk  71K Feb 28  2024 announcement-17.0.2.tgz.gpg
-rw-rw-r--   1 asterisk asterisk 887K Apr 17  2023 api-16.0.11.tgz.gpg
-rw-rw-r--   1 asterisk asterisk 887K May 26  2023 api-16.0.12.tgz.gpg
-rw-rw-r--   1 asterisk asterisk 887K Sep 30  2023 api-16.0.13.tgz.gpg
-rw-rw-r--   1 asterisk asterisk 1.1M Jul 23  2024 api-17.0.1.5.tgz.gpg
-rw-rw-r--   1 asterisk asterisk 1.1M Nov 15  2024 api-17.0.1.6.tgz.gpg
-rw-rw-r--   1 asterisk asterisk 1.1M May 12  2025 api-17.0.1.7.tgz.gpg
...

When was this system purchased? Was it back in 2022 around the time of the November announcement? The timing of all of that sounds like it put you over a barrel.

The most direct replacement for the High Availability feature is the Advanced Recovery module. Besides being actively developed, AR is commercially supported by Sangoma if you run into any issues. :foot: :beetle:

Presuming you mean this announcement on the FreePBX blog about EOL of v13 & v14 ?