Upgrades

Handle plugin update errors, version conflicts, and post-update issues.

Always back up before upgrading

bash
sp export --name pre-update
sp update creates an automatic backup before applying changes, but a manual export gives you a named, easy-to-find restore point.

Plugin update fails

If sp update plugins fails:

  1. Check your internet connection on the VPS
  2. Check that the distribution server is reachable
  3. Wait a few minutes and retry — the distribution server may be temporarily unavailable
  4. Contact support if the problem persists
bash
# Retry the update
sp update plugins

Mautic shows errors after plugin update

Clear the Mautic cache first — most post-update errors clear after a cache flush:

bash
sp restart mautic

If errors persist, check the Mautic logs for PHP exceptions:

bash
sp logs mautic --tail 200

Share the log output with support via the support form.

Rolling back after a failed update

bash
sp restore --file ~/sp-backups/pre-update.tar.gz

CLI update breaks commands

If the sp command stops working after a CLI update, reinstall it from scratch:

bash
curl -fsSL https://raw.githubusercontent.com/aimaddotnet/serviceplus-cli-releases/main/install.sh | bash

If the latest release has a known issue, contact support — they can point you to a specific version to install.

Post-update checklist

  • Run sp status — all services should show as running
  • Log in to Mautic and verify the dashboard loads
  • Check that n8n workflows are still active and running
  • Send a test email from Mautic to confirm SMTP is still working
Performance