# Applying the new Update to 4.5 broke my PBX
**URL:** https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778
**Category:** VitalPBX
**Created:** [December 15, 2024, 11:43pm UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778 "2024-12-15T23:43:28Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@lifeline](https://forums.vitalpbx.org/u/lifeline)
#### Post date: [December 15, 2024, 11:43pm UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778/1 "2024-12-15T23:43:28Z")
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!
1. 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.
2. 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!
---
### Author:  [@PitzKey](https://forums.vitalpbx.org/u/PitzKey)
#### Post date: [December 15, 2024, 11:49pm UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778/2 "2024-12-15T23:49:15Z")
Hi @lifeline,
> [@lifeline](#):
>
> Turn on the comments on the forum post that announced the update so people can post this stuff
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.
> [@lifeline](#):
>
> Don’t push out an update or version for that matter until its tested
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…
---
### Author:  [@mo10](https://forums.vitalpbx.org/u/mo10)
#### Post date: [December 16, 2024, 12:39pm UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778/3 "2024-12-16T12:39:24Z")
I had [this ioncube Error](https://forums.vitalpbx.org/t/v4-5-script-error-the-ioncube-loader/4720), but that was after migrating from 4.2 to 4.5
Was it the same Error for you, but a regular update from 4.5 to 4.5 R3?
---
### Author:  [@lifeline](https://forums.vitalpbx.org/u/lifeline)
#### Post date: [December 16, 2024, 1:52pm UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778/4 "2024-12-16T13:52:29Z")
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.
---
### Author:  [@miguel](https://forums.vitalpbx.org/u/miguel)
#### Post date: [December 17, 2024, 11:45am UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778/5 "2024-12-17T11:45:38Z")
Use the command line to run the update and share any errors if any happened.
`sudo vitalpbx update`
---
### Author:  [@system](https://forums.vitalpbx.org/u/system)
#### Post date: [January 16, 2025, 11:45am UTC](https://forums.vitalpbx.org/t/applying-the-new-update-to-4-5-broke-my-pbx/4778/6 "2025-01-16T11:45:57Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.