Solved FreePBX 14 Module Update Errors
-
I am seeing similar issues on version 13
-
@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.
-
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
-
Framework is updated now too.
-
-
@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
-
@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.
-
Core and framework updated again.
-
@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
-
@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.
-
@jaredbusch said in FreePBX 14 Module Update Errors:
Core and framework updated again.
Busy day there!
-
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.
-
Appears to be a bug with the firewall not using the trusted zones properly.
-
@syko24 said in FreePBX 14 Module Update Errors:
Appears to be a bug with the firewall not using the trusted zones properly.
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.
-
@jaredbusch said in FreePBX 14 Module Update Errors:
@syko24 said in FreePBX 14 Module Update Errors:
Appears to be a bug with the firewall not using the trusted zones properly.
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.
So far 13.0.54.3 seems to be working. Thanks @JaredBusch
-
It must be the week of bad updates or something.
I cannot remember the last time they had a string of bad updates like this.
I update systems monthly-ish and have not had a problem since sometime last year.
-
@jaredbusch said in FreePBX 14 Module Update Errors:
It must be the week of bad updates or something.
I cannot remember the last time they had a string of bad updates like this.
I update systems monthly-ish and have not had a problem since sometime last year.We did not upgrade or release any firewall versions this release. The last firewall version published to the STABLE track is 19 days old.
The only one in edge is:
- There are 198 systems using version 13.0.55.3 of firewall (94051). It is 2 days old
- There are 1 systems using version 13.0.55.2 of firewall (94041). It is 2 days old
I wouldn't say it was a week...It was one day of pushing moving EDGE modules to STABLE that required other modules that weren't released (core required a version of framework that was in edge, ivr required core that wasn't released at the same time as core was, it was release about an hour later).
-
@tm1000 I was not complaining. I was actually stating that I have never seen as many issues at once before, ever. You guys do a great job.
-
@jaredbusch said in FreePBX 14 Module Update Errors:
@tm1000 I was not complaining. I was actually stating that I have never seen as many issues at once before, ever. You guys do a great job.
Thanks Jared. Just explaining what went wrong for those curious. I'll push the firewall issue to Rob later today
-
Rob just got back to me and swears the trust code hasn't changed in a long time but he'll look at it later today