Version 4.5 uses Debian v12, while 4.2.0-1 is using Debian 11 so currently no direct upgrade path exists yet.
Currently on the site they are only showing an ISO available for version 4.5 so setting up a new vm with the ISO is the only way right now to get 4.5. The VPS install script is not yet upgraded either to install version 4.5, but I would guess they will work to get the script upgraded.
Not sure if they will provide the script to do the inplace upgrade from Debian 11 to Debian 12 and then setup the new 4.5 version so until they say something else, most likely backup and restore to Debian 12 server
Upgrading to VitalPBX 4.5 is easy and will immediately enhance your VoIP experience. Visit our website for detailed upgrade instructions and full release notes.
So I hope it will be as easy as promised and instructions are released soon.
Do you have a working link to download the 4.5 ISO? I’m surprised they announced the release 4 days ago but still have the giant download button that says “VitalPBX 4.5” which links to 4.0.
As a test I tried doing the base upgrade to Debian 12, then updated the vitalpbx.list file from “v4” to “v4.5” after doing a little research and finding that apt repo out there. However, I might have chosen the wrong option or something else went wrong because now I get an Apache Forbidden page. I’ll just restore from my snapshot.
I’m thinking the method to build from the new ISO and then restore the backup file is the best approach to upgrade just like when we went from v3 to v4.
No, I assumed the link they had was already the 4.5 one as that is what it says in the webpage. I guess they are still working on getting the proper links in the site.
From the release notes, they have swapped over to nginx for the webserver so if you were getting apache errors it must not have been properly removed.
I guess for now the best thing is to wait until the vital devs properly publish the 4.5 stuff properly.
Note: You might see some nginx errors while upgrading, you can ignore those for now.
Stop and disable apache2 service again (it probably restarted during the upgrade)
Remove old packages
apt autoremove
apt remove apache2
Check nginx config nginx -t, if it gives you an error about a duplicate server, simply remove the default server config rm /etc/nginx/sites-enabled/default and restart nginx nginx -s reload
I installed using the script under a fresh debian 12 installation and restored our backup. No issues so far. The ISO still downloads v4.0 as of this morning
Hello Mr Cuadra,
Thank you for the script. I have used it and currently have an information display error.
It is not displayed under System Usage (CPU/Memory), Server Uptime, Firewall and under PJSIP Endpoints/Trunks (Contacts/Match). I have attached a picture, do you have any idea how I can reactivate the displays?
Edit the file /usr/share/vitalpbx/monitor/config.ini and change the value localhost to 127.0.0.1 in the [asterisk] section. Finally, restart the vpbx-monitor service.
I agree 100%, I don’t know how other companies work but we can’t be taking production servers down for complete rebuilds every year. Between extra hardware needs to run 2 simultaneous systems to minimize down time and the overtime costs to have senior techs working late at night during down hours greatly increases the cost of ownership of VitalPBX and will cause users to start looking for alternatives.
VitalPBX needs to come up with a smoother upgrade process then continual reinstalls.
