Looking for a tech with vitalpbx expertise to help migrate

Looking for a tech with vitalpbx expertise to help migrate.
This may be a contract to hire position.
Please contact [email protected]

1 Like

VitalPBX actually offer a service where you can hire them to assist you. We’ve done it and it was incredibly helpful.

1 Like

TCE, what is the name of this service? I couldn’t locate it on the website.

1 Like

Migration isn’t too difficult actually.
1: Setup new server on using default Debian 12 and run the VPBX setup script. Use the same root password as current server - important also note your credentials for any add ons.
2: Add your client IP to the firewall white list and any other future IPs that may be needed on the current setup. Then Backup current/old server using the backup feature but tick everything. Also screenshot what ‘add-ons’ you are using so you can remember to add them later.
3: Click the VPBX user drop down top right and click license info. Snapshot that and choose Revoke.
4: Switch the A record in the DNS entry now to new server IP.
5: Log into the VPBX web page on new server. Add your license and then add your ‘add-ons’ but make sure you check each add on is working but going to its individual web page and running through the wizard for each. Use same credentials used before.
6: Restore from backup and reboot.
7: Go through all settings and make sure things like PJSIP settings have your new IP saved.
8: Go into the certificate folder ( cd /usr/share/vitalpbx/certificates/ ) via ssh and delete the xyz.com folder. Now go back into the web interface and get it to fix the a certificate by running “update” on that page. Once done - go through all settings that reference the certificate.
9: That should be it.

Also ref:

NB: If you skipped the wizard step for add-ons before restoring backup and you get error 500 website pages when trying to run the Sonata features. When this happened to me, Jose figured out that there was privilege issues to do with the database on multiple of the Sonata apps and an issue with Vitxi where it needed to optimize, clear cache, re-add firewall rules and restart it.