Well, I went to change the Follow-Me List in an extension, then Submitted it, get an error as “Whoops \ Exception \ ErrorException (E_WARNING) Trying to access array offset on value of type bool” but still I can Apply Change however it fails to save the change:
grep -i “array offset” /var/log -R 2>/dev/null
/var/log/asterisk/firewall.log:PHP Warning: Trying to access array offset on value of type null in phar:///var/www/html/admin/modules/firewall/hooks/voipfirewalld/firewall.php on line 25
Anyone know how to resolve this issue? Thanks!
Going to split this out into a new topic… but were there any extensions that failed to restore ?
All the extensions restored and seem to be working. (I have not moved the commercial modules, was waiting for the weekend, but in and out calls, voice mail, faxes, all seem to be working.)
Also of note, if I change the extension secret, I get the same error but it saves and keeps the new secret post apply, but of course that is not an array.
Just to note since this is a new thread, I migrated from v16 to v17, from a full backup. This issue is only in V17.
Any ideas?
I ran: SELECT * FROM findmefollow WHERE grpnum=‘101’;
102-103
So I updated the DB as follows:
UPDATE findmefollow SET grplist=‘102-103-17035551212#’ WHERE grpnum=‘101’;
Query OK, 1 row affected (0.001 sec)
Rows matched: 1 Changed: 1 Warnings: 0
SELECT * FROM findmefollow WHERE grpnum=‘101’; Looked correct: 102-103-17035551212#
Looked incorrect in the GUI, I still see only 102-103
Ran : fwconsole reload
It still only see 102-103 in GUI AND DB after the reload shows
SELECT * FROM findmefollow WHERE grpnum=‘101’;
102-103
Feels like something in FreePBX is regenerating the findmefollow table from another internal source during reload?
So, I made a brand new extension, with Follow-Me List as 888-101-17035551212#, saved it. NO warning and after applying the changes, the follow-me data persisted and was correct.
If I change any existing extension follow-me list it throws the error and fails to actually save the change, whereas a new extension saves as expected.
Perhaps I just rebuild all the existing extensions as a new extension, test and if it registers and all is okay, then delete the original extensions and recreate them in full. Unless someone has a better idea?
Is there some additional null character or whitespace in those fields ?
This sounds like something for the issue tracker… which does not seem to have any similar open issues right now regarding the problem you are experiencing – although there were some closed ones that might be related:
No I think maybe my issue. I mentioned earlier that I had not deactivated and reactivated the commercial modules thinking it would not matter.. What I finally did this weekend after nothing was working, as I had not deactivated the commercial modules from the V16 freepbx in case I had to fall back, and as I had migrated with a full backup to the v17 server but without the commercial licenses in tow, it dawned on me to disable all commercial modules on the v17 server, that were licensed on the old server and any other ones that seemed activated on V17, I guess from just activating the V17.. Disabling the commercial modules cleared the issue up and I could save follow-me as expected, probably as the commercial endpoint manager was one of the modules I disabled of about 10 commercial modules I have on V16. So today is first production test, and seems to be working. If no issues this week I will deactivate the V16 freepbx and reactivate the commercial licenses to V17 this coming weekend, though I will still probably leave most disabled for now. I will also though backup first. I don’t do migrations like this, ever, so it was a frustrating learning journey for me to say the least. On the other hand, have to love freepbx when it is working well. So I take the blame for what seems to be a self-inflicted fiasco.
So I deactivated the old server this morning, and reactivated the id on the new server, so the licenses transferred over.
I had a heck of a time getting back on to the new server web admin page, it kept complaining about ssl and just bounced me out. Somehow I finally worked though that via cli, I think by disabling the sysadmin module and re-enabling it a few times.
The only issue remaining that I am aware of, assuming it is not system wide, is that both servers now in the GUI Admin → Module Admin, if I ty to check for module updates I get “Warning: Cannot connect to online repository(s) (https://mirror.freepbx.org). Online modules are not available.”
It seems to update though via cli fwconsole ma updateall
I will wait and see, unless someone knows if the module update system is misbehaving at mirror.freepbx today 5/23/2026 or if no issues there, knows why I might be having this issue via GUI module updates post license re-activation process.
Thank you!
Note: Later on 5/23/2026 - module updates are working now, so the earlier issue was the module update system misbehaving at mirror.freepbx