Update Blesta: The Safe, Proven Checklist to Avoid Disasters

When you update Blesta, the update itself is usually quick: upload the new files, click a button. Problems come from what you didn’t check first: a plugin that isn’t ready for the new version, a PHP version that’s too old, or no backup to fall back on. This checklist is the routine we follow on our own installs, based on Blesta’s official upgrade guide, plus the lessons we’ve picked up along the way.

Why You Should Update Blesta Regularly

Your billing system holds client details, invoices and the keys to your servers. Each release fixes bugs, and some fix security issues. Staying current also keeps you compatible with newer PHP versions and with the latest plugins, which often require a recent Blesta. The longer you wait, the bigger the jump, and big jumps are where things go wrong. Small, regular updates are the safest way to update Blesta.

Before You Update Blesta

1. Read the release notes

Patch releases (6.0.2 to 6.0.3) are usually bug fixes. Minor and major releases can change requirements or behavior. For a major jump, such as 5.x to 6.0, read Blesta’s migration guide in full. Blesta 6 needs PHP 8.2 or newer and rebuilt the staff area on Bootstrap 5.

2. Check your license covers updates

Owned licenses need active Support & Updates to install new versions. The System Status widget on the Blesta dashboard shows this.

3. Check your server

Compare the new version’s requirements with your server: PHP version, required PHP extensions and the ionCube Loader. Blesta’s core files are encoded, so the loader on your server must be new enough for the release you’re installing. If you plan to upgrade PHP at the same time, do that first, update the ionCube Loader to match, and check Blesta still runs before you update Blesta itself. Changing one thing at a time makes problems far easier to trace.

4. Check your plugins, modules and theme

List every third-party extension you use and check each supports the new version. If you’ve customized the client template, note which files you changed. That’s one reason we recommend customizing a copy of the template, not the original.

5. Back up everything

Blesta’s docs say to make a manual backup of everything before upgrading. That means the database and all files. Make sure the backup includes config/blesta.php, which holds your database details and the encryption key Blesta uses for sensitive data. Without that key, a restored database can’t read its encrypted data.

6. Pick a quiet time

Avoid updating just before invoices generate. You can put Blesta into maintenance mode under Settings > System > General > Maintenance while you work, so clients see a friendly notice instead of half-finished pages.

Test the Update on a Copy First

The best way to update Blesta without surprises is to do it twice: once on a test copy, then for real. Copy your files and database to a test subdomain, point the copy’s config/blesta.php at the copied database, and turn off the cron and outgoing email on the copy so it can’t bill or email real clients. Update the copy, click around, and only then update your live install. We keep a permanent dev copy for exactly this, and it has caught plugin problems more than once.

How to Update Blesta: Running the Upgrade

1. Download the new version from your Blesta account’s Downloads area.
2. Unzip it and upload the contents of the blesta folder over your existing install, overwriting the old files.
3. Run the upgrader, either in the browser by visiting /admin/upgrade and clicking Continue with Upgrade, or from the command line in your Blesta folder:

php ./index.php admin/upgrade

Blesta 6 can also run it unattended with php ./index.php admin/upgrade -y. On large installs the command line is the safer choice, because a browser can time out partway through a database upgrade. If your host has several PHP versions, call the same one your site uses, for example /opt/cpanel/ea-php83/root/usr/bin/php on cPanel servers.

Updating Plugins and Modules

Third-party plugins and modules update separately from Blesta. Upload the new plugin files over the old ones, then click Upgrade next to the plugin in Blesta. That runs the plugin’s own upgrade steps, such as adding database columns. When you update Blesta and several plugins on the same day, do Blesta first, test it, then do each plugin one at a time. If something breaks, you’ll know exactly which change caused it. Our plugin install guide covers the upload steps in detail.

What Actually Changes During an Update

It helps to know what the upgrader touches. Uploading the new files replaces Blesta’s core code, the default templates and the bundled modules, gateways and plugins. Your own files, such as third-party plugins and a custom template copy, are left alone, and so is config/blesta.php, as long as you don’t delete it. Running the upgrader then changes the database: it adds new tables and columns, updates settings and records the new version number. Your clients, invoices and services stay exactly as they were.

This is also why a half-finished upgrade is risky. If the files are new but the database is old, or the other way round, Blesta can behave strangely until both match.

After You Update Blesta

• Check the version. The installed version shows in the footer of the staff area.
• Upgrade your plugins. Under Settings > Company > Plugins, click Upgrade on any plugin that offers it. Do the same for modules under Settings > Company > Modules.
• Check the cron. Settings > System > Automation should show a run within the last minute or two. See our Blesta cron job guide if it doesn’t.
• Test the client area. Log in as a test client, view an invoice, open a ticket and use any plugin pages.
• Place a test order if the release touched ordering, payments or modules.
• Clear your browser cache if pages look broken. Old CSS and JavaScript files are a common cause of odd layouts right after an update.
• Turn maintenance mode off.

If Something Goes Wrong

Don’t keep clicking the upgrader. Check the error, then check the database_version value in the settings table, which shows how far the upgrade got. Blesta’s upgrade guide has a section on failed upgrades. If you can’t fix it quickly, restore your files and database from the backup you made in step 5, and try again once you know the cause.

The most common problems we see when people update Blesta are:

• A blank page or ionCube error: the PHP version or ionCube Loader is too old for the new release.
• A plugin page errors out: the plugin needs its own update for the new Blesta version. Disable it until one is available.
• The client area looks wrong: a customized template is missing changes from the new release. Compare it with the new default template.
• The upgrader stopped partway: usually a browser timeout. Restore the backup and run it from the command line.

Plan Your Rollback Before You Start

A backup only helps if you know how to restore it. Before you update Blesta, write down the steps: where the backup lives, how to import the database, and how to put the old files back. Time how long a restore takes on your test copy. Then, if the live update goes badly at 11 p.m., you follow a list instead of guessing. Keep the old version’s zip file too, so you can put the exact old files back without hunting for them. If your host offers server snapshots, take one right before you start as well; restoring a snapshot is often the fastest rollback of all.

A Simple Monthly Routine

For a small hosting business, this routine takes under an hour a month and keeps you from ever falling far behind:

1. Check for new Blesta, plugin and module releases.
2. Read the notes and decide what to install.
3. Refresh your test copy from a fresh backup.
4. Update the test copy and run your checks.
5. Update Blesta on the live site during a quiet hour, then repeat the checks.

Frequently Asked Questions

How often should I update Blesta?

Check for new releases at least monthly. Apply security releases promptly. For feature releases, waiting a week for any quick follow-up patch is reasonable, especially if you rely on third-party plugins.

Will updating remove my plugins?

No. Third-party plugins live in their own folders and aren’t part of the Blesta download. Check they support the new version, then upgrade them from the Plugins page if needed.

Can I skip versions when I update Blesta?

Usually yes: the upgrader runs every database step between your version and the new one. For big jumps, read the notes for each major version you’re skipping, and always test on a copy first.

Should I tell clients before an update?

For a quick patch during a quiet hour, maintenance mode is usually enough. For a major version that may take longer, a short notice a day or two ahead is a nice touch, especially if clients pay invoices at set times.

Can someone update Blesta for me?

Yes. Contact us and we can handle the backup, update and testing. Learn more about keeping Blesta safe in our Blesta security guide, and see all our Blesta plugins and guides.