Group Manager permissions will not save

question

New Member
Mar 30, 2026
11
0
1
64
I cannot set or clear any permission in Group Manager heading XML CDR. It is the same for anything under anything about Voice Mail. Saving resets it to how it was.

I can successfully change permissions for Access Controls and other heading items at the top of the list.

Everything under Permissions heading is enabled. I am logged in as admin with superadmin privileges. I have seen this issue by searching the internet but the fixes I have tried have not worked.
 
This issue has existed for years already. I found myself having to make the changes from the database manually. FS PBX, an alternative to what you are using today, solves a lot of these bugs including this one.
 
This issue has existed for years already. I found myself having to make the changes from the database manually. FS PBX, an alternative to what you are using today, solves a lot of these bugs including this one.
Do you know if anyone has run FS PBX on Amazon AWS t3.micro instance (1GB 2 CPU)? I am currently running FusionPBX on that.
 
Last edited:
I think 4 GB of ram is the minimum requirement, otherwise it will work fine on AWS. No, it is not ram intensive while running normally; it’s just the initial build process that demands the ram
 
I think 4 GB of ram is the minimum requirement, otherwise it will work fine on AWS. No, it is not ram intensive while running normally; it’s just the initial build process that demands the ram
I installed FS PBX on a 4 GB t3.medium instance to compare. 4 GB is the minimum memory to install, but after installation it looks like I could save the AMI image and install it on a 2 GB t3.small instance. Here is the memory use comparison while logged into their GUIs.

FS PBX on 4 GB t3.medium
total used free shared buff/cache available
Mem: 3955172 1405828 2483564 59332 343300 2549344
Swap: 1048572 0 1048572

FusionPBX on 1 GB t3.micro
total used free shared buff/cache available
Mem: 962280 526260 179288 40296 437212 436020
Swap: 1048572 0 1048572

Since I am the only tenant on my PBX I can probably keep using the 1 GB AMI instance with FusionPBX. But FS PBX is more polished and documented IMO.
 
I cannot set or clear any permission in Group Manager heading XML CDR. It is the same for anything under anything about Voice Mail. Saving resets it to how it was.

I can successfully change permissions for Access Controls and other heading items at the top of the list.

Everything under Permissions heading is enabled. I am logged in as admin with superadmin privileges. I have seen this issue by searching the internet but the fixes I have tried have not worked.

PHP by default has a limit for the size of an HTML form. There is a simple work around use the category drop down or a search term to reduce the size of the HTML form. As long as it reduces the size small enough to work with the php.ini default then it will work and the value will save.

These are controlled in the php.ini the install script for FusionPBX usually takes care of these.

This will get your version of PHP
php -i | grep php.ini

Here are some sed command line commands that can change the values in you PHP.ini file. If your version of PHP is not 8.2 then you would need to adjust the command to match your version of PHP.
/usr/bin/sed 's#post_max_size = .*#post_max_size = 80M#g' -i /etc/php/8.2/fpm/php.ini
/usr/bin/sed 's#upload_max_filesize = .*#upload_max_filesize = 80M#g' -i /etc/php/8.2/fpm/php.ini
/usr/bin/sed 's#;max_input_vars = .*#max_input_vars = 15000#g' -i /etc/php/8.2/fpm/php.ini

The FusionPBX install increase the value of these settings in the php.ini. However, upgrading PHP could set the php.ini values back to it's defaults.

I'll fix this and build the solution into the code so that this issue is resolved permanently.
 
SOLVED this issue has been permanently fixed in FusionPBX 5.5 and higher.

- This issue is now fixed in FusionPBX 5.5 latest code and Master branch.
- The setting for max_input_vars is now large enough by default and set as a runtime value so that it is no longer an issue.

So for those using FusionPBX another WIN among many other recent improvements.