We’ve released a turnkey installer for Open Source SystemAdmin module on Incredible PBX 2025-U and IncrediblePBX 2027-U platforms:
cd /tmp
wget https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/SystemAdmin-OpenSource/install-systemadmin
chmod +x install-systemadmin
./install-systemadmin
sed -i 's|<supported>17.0|<supported>16.0|' /var/www/html/admin/modules/systemadmin/module.xml
sed -i 's|<version>17.0.1|<version>16.0.1|' /var/www/html/admin/modules/systemadmin/module.xml
Are you releasing your own version of the module and supporting its use on FreePBX 16?
Nope and Nope. Just trying to save everyone a little time.
Free to use or modify as desired pursuant to AGPL 3.
When saving an email config, it outputs an array of data at the top of the page. That shouldn’t be there.
If you save the config with TLS disabled, the Remote form doesn’t display. But then everything is displayed under the Local form. However, if you save it again from the Local form, the display starts to work right.
While the displays are not correct and everything is displayed in the Local form, no validation is done on the mail server allowing for a malformed server name to be used. Validation exists when the Remote form is displayed properly.
It also doesn’t seem to detect the time zone of the server properly on the Time Zone page.
Even after you select the proper time zone and hit save, the page just reloads showing “Africa”. It never displays the system time zone properly.
For the Packet Capture section, there should be defaults for Max File Size, Max File Count, Packet Count. Either for one, two or all because without those set, someone can end up starting a capture that will run until it is stopped.
The option icons for the packet captures should be bigger and the icon for Stop should be a stop sign at least. The X icon makes it look like a delete…
Also, tooltips. Not a single form has any tooltips to explain what is what and any help/info text for each of the form elements. That would be super helpful. Perhaps even some more help text for some of these forms.
Thanks to all for the Bug reports. I’ve created a todo-List and will work on the issues but I can’t say when I will have time to take care of it again.
Yes, because of this, an email will be sent if a packet capture runs for more than 24 hours. You can find the code here. It is run as a FreePBX job. But it might really be better to offer the option you mentioned as well.
I’ve created a new version with resolves the following bugs:
I’ve uploaded it to the mentioned GitHub repository.
@NerdUno Could you remove the “mkdir /dev/md” from your install instructions if the fix works for you?
To replicate the bug, could you please provide the following information:
The error message indicates that the network settings are being generated by netplan. According to the error message, it seems that a bonding device is being used. Could you please post the contents of the netplan configuration files? Feel free to anonymize them if they contain confidential information. Was it an on-premise or a cloud installation? If it was a cloud installation, which provider did you use?
The error popped up using Incredible PBX 2027-U on Proxmox which uses Ubuntu 22.04 and FreePBX 16. Wandered off the reservation a bit and adjusted our installer to eliminate the problem by forcing the download and adjusting the supported FreePBX version:
cd /tmp
wget https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/SystemAdmin-OpenSource/systemadmin-1.0.0-Ubuntu22-04.deb
apt install ./systemadmin-1.0.0-Ubuntu22-04.deb
rm -f systemadmin-1.0.0-Ubuntu22-04.deb
mkdir /dev/md
echo "network:
ethernets:
ens18:
dhcp4: true
version: 2" > /etc/netplan/incrediblepbx.yaml
fwconsole ma download https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/SystemAdmin-OpenSource/systemadmin.tar.gz --force
sed -i 's|<supported>17.0|<supported>16.0|' /var/www/html/admin/modules/systemadmin/module.xml
sed -i 's|17.0.1|16.0.1|' /var/www/html/admin/modules/systemadmin/module.xml
sed -i 's|Initial|Modified by NerdUno|' /var/www/html/admin/modules/systemadmin/module.xml
fwconsole ma install systemadmin
TangoPBX is a little different beast since they use the older 22.04 version of Ubuntu but the newer version of FreePBX. Incredible PBX platforms match the latest versions with the latest versions, e.g. iPBX 2025 uses 24.04 and FreePBX 17 while the older iPBX 2027 uses 22.04 and FreePBX 16. Not to worry, we’re odd, too. iPBX 2025 is a newer release than iPBX 2027 which was designed a couple years ago to provide a stable platform until 2027. Hope this helps.
This is happening because bonding_masters is obsolete for netplan. It’s not a valid netplan option, it’s an old option from /etc/network/interfaces. The netplan version on Ubuntu 24.04 is newer than 22.04 and the newer version is less forgiving and has much more strict enforcement in YAML. It is possible the 22.04 version is just ignoring the bad config entry but the 24.04 version is not liking it because it’s doing more strict enforcement.
Remove bonding_masters from the incrediblepbx.yml and try again.
@Hannes I’m having trouble untarring the latest release which says it’s not in gz format:
https://github.com/hannes427/systemadmin_php/blob/master/install/systemadmin.tar.gz
@AMI Sorry but our iPBX 2027 release had no .yml or .yaml file at all. The only way I could get the errors to go away was to create the one shown above in the install script.
Then it might be how Ubuntu is being installed. Netplan doesn’t create a config by default that is generally done by the Ubuntu installer or cloud-init (when installing in the cloud) so you end up with either /etc/netplan/00-installer-config.yaml or /etc/netplan/50-cloud-init.yaml. It also not be installed if NetworkManager was used to control the network originally.
If /etc/netplan is empty and Netplan has been made the main network manager, it’s going to throw errors and cause issues. So the module wants to use netplan for the network management and it sounds like the IPBX setup doesn’t generate the netplan configs because another application is controlling the network.
netplan get << prints the netplan configuration
netplan generate << validates the yaml
netplan apply << applies the configuration
Basic netplan config:
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: true
The end user installs Ubuntu, not the Incredible PBX installer. In my case, I installed Ubuntu into Proxmox using the Ubuntu ISO and all of its Ubuntu defaults. There was no netplan option for network management. Might I suggest you download the Ubuntu 22.04 ISO for yourself and take it for a spin. The only netplan data was what I documented creating above to make the SystemAdmin errors go away:
echo "network:
ethernets:
ens18:
dhcp4: true
version: 2" > /etc/netplan/incrediblepbx.yaml
I don’t have a system here to install this on. All my Ubuntu 24.04 systems are in the cloud and use cloud-init to install them. It generates the netplan config.
I also understand the user installs the OS hence my saying it might have been on it was installed. The extra stuff was offered to help troubleshoot and even be used to check if netplan has a config during the install process if this module is going to be used.
TangoPBX uses an ISO for installs. Incredible PBX relies upon Ubuntu and Debian ISOs as the presumed install mechanism. So your use of cloud-init is the special use case. If I were developing a module, it would support the traditional use case, not the exception as you have suggested.
Which version did you use for Ubuntu 24.04? desktop, live, netboot?
Yes, this is because of if you open this link with wget GitHub sends a html-file. Either open this URL in a web-browser and click on “Raw” respectively “view raw” or if you want/need to use wget please use the url https://github.com/hannes427/systemadmin_php/raw/refs/heads/master/install/systemadmin.tar.gz
Thank you for your reply. In addition to AMI’s question about the Ubuntu version: Which Proxmox version are you using? I have never worked with Proxmox, but maybe the issue is related to the Proxmox version, which uses an outdated option (“bonding_masters”) when creating an Ubuntu image?
Since I don’t have Proxmox available, I’m trying to replicate the issue without Proxmox for now. If that doesn’t lead to a solution, I will see if it’s possible to install Proxmox on a virtual machine for testing purposes.
We used Ubuntu 22.04.3 Live Server ISO with the minimal install option. And we use Proxmox 8. For about $300, it’s the best development platform for your toolbox (32GB RAM, 1TB storage). Our Wiki will walk you through everything. I can’t say enough good things about Proxmox. It’s open source, free, and based upon Debian 12.5. It has no equal, and we’ve tried almost all of them including many decades with VMware and many years on VirtualBox, Oracle Cloud and Amazon’s EC2 and S3, Digital Ocean, Vultr, and many more. Save your money!