I had 4.5 running on a production server. I saw the new update that fixed some of the bugs in 4.5 come out a few days ago. But, I thought I would wait a few days before installing to make sure there were no problems with the update. I have been checking the forums and hadn’t seen any, so I thought I would go ahead on a Sunday and do the update.
I got an ioncube error and requirement to install it, so now I am recovering my production PBX from a backup because I dont have time to troubleshoot and install the correct version of ioncube while its down.
You guys cant keep pushing stuff out that breaks production servers!
Turn on the comments on the forum post that announced the update so people can post this stuff, so we can make an informed decision about an update.
Don’t push out an update or version for that matter until its tested.
I have been in the PBX business for 17 years and started the move to VitalPBX this year and I have never in 17 years worked with a provider that would send out version changes or updates that would break a production server.
I love the VitalPBX platform so far, but when people depend on me, I have to be able to depend on you!
An announcement post is dedicated and pinned for announced purposes.
It’s best to create a topic for every issue you experience, that way discussions are staying on topic and things can get properly addressed.
I can’t speak for the VitalPBX team, but updates are usually tested before they are shipped to the stable repos.
I know you are already restoring from backup. But have to recorded the errors and logs. Others may not be able to reproduce this issue…
This was a fresh install of 4.5 on Debian 12 and has been working well for a week or more, besides the regular bugs that were reported with 4.5. I simply clicked check for updates, saw the update and ran it.