Solved FreePBX 14 Module Update Errors

[scottalanmiller]

Found the issue, Core needs to update but Core 14.0.18.16 depends on FreePBX Framework 14.0.3.4. But FreePBX Framework has only been released up to 14.0.3.2. So for the moment, there is nothing to be done. This is a FreePBX repo bug, and Sangoma is aware. It's on their list for weekly triage. At the moment, though, no fix.

[scottalanmiller]

Ah, found a way around it. Select alternative versions for Core, and "rollback" to Core 14.0.18.8. This is the top version that works with the latest available FreePBX Framework.

[ss4sgoku]

hi i have the same problem how can i roll back it? please helpme

[JaredBusch]

@ss4sgoku said in FreePBX 14 Module Update Errors:

hi i have the same problem how can i roll back it? please helpme

You go in and check for updates to your modules by clicking the Check Online button. Then you expand the module you want to downgrade and roll back to the version you want.

[scottalanmiller]

@ss4sgoku it says "previous" and then "rollback" even when going forward. Not good display logic there, but it functions well.

[JaredBusch]

@scottalanmiller said in FreePBX 14 Module Update Errors:

@ss4sgoku it says "previous" and then "rollback" even when going forward. Not good display logic there, but it functions well.

The button could cosmetically be updated to show update or rollback based on version comparison. but seriously most people will almost never see this.

I assume this is part of the open source version so it could be fixed by some enterprising individual.

[netprimates]

I am seeing similar issues on version 13

[scottalanmiller]

@netprimates said in FreePBX 14 Module Update Errors:

I am seeing similar issues on version 13

Not surprised, they probably did the same bad release across the board.

[netprimates]

I assume you are referring to repo bug [17585] - https://issues.freepbx.org/projects/FREEPBX/issues/FREEPBX-17585?filter=allissues which seems to have been closed

[JaredBusch]

Framework is updated now too.

[JaredBusch]

[scottalanmiller]

@netprimates said in FreePBX 14 Module Update Errors:

I assume you are referring to repo bug [17585] - https://issues.freepbx.org/projects/FREEPBX/issues/FREEPBX-17585?filter=allissues which seems to have been closed

Yes

[tm1000]

@netprimates said in FreePBX 14 Module Update Errors:

I assume you are referring to repo bug [17585] - https://issues.freepbx.org/projects/FREEPBX/issues/FREEPBX-17585?filter=allissues which seems to have been closed

Closed with a resolution. Not just closed.

[JaredBusch]

Core and framework updated again.

[tm1000]

@jaredbusch said in FreePBX 14 Module Update Errors:

Core and framework updated again.

Which fixed a codec read issue with Asterisk 13.9 and lower

[JaredBusch]

@tm1000 said in FreePBX 14 Module Update Errors:

@jaredbusch said in FreePBX 14 Module Update Errors:

Core and framework updated again.

Which fixed a codec read issue with Asterisk 13.9 and lower

Thanks. I had not yet looked into the change log.

[scottalanmiller]

@jaredbusch said in FreePBX 14 Module Update Errors:

Core and framework updated again.

Busy day there!

[syko24]

Not sure if anyone else is experiencing this issue but after installing all the module updates yesterday all my clients using chan_sip trunks from voip.ms are being added to the blacklist under intrusion detection. I ended up having the add them to the whitelist to prevent issues. Clients using pj_sip trunks seems to be fine though.

[syko24]

Appears to be a bug with the firewall not using the trusted zones properly.

https://community.freepbx.org/t/bug-in-latest-firewall-adding-ip-to-firewall-trusted-zone-no-longer-updates-iptables-firewall-rules-on-firewall-restart/50181/6

[JaredBusch]

@syko24 said in FreePBX 14 Module Update Errors:

Appears to be a bug with the firewall not using the trusted zones properly.

https://community.freepbx.org/t/bug-in-latest-firewall-adding-ip-to-firewall-trusted-zone-no-longer-updates-iptables-firewall-rules-on-firewall-restart/50181/6

Roll back to the previous Firewall for now.

Check for updates and then expand firewall and then go to previous and rollback to the one you want.