Change a DigitalOcean server plan or storage allowance in Blesta

Skip to main content
Print

Change a DigitalOcean server plan or storage allowance in Blesta

Use the supported Blesta service-change workflow when a customer needs a different Droplet plan or more attached storage. Review the resource change independently from the resulting billing price or package label.

Check the target before offering it

A plan resize needs the server to power off; the module handles the power sequence. Allow for downtime that depends on the operation rather than promising a fixed short interruption. Arrange maintenance and take an appropriate backup before proceeding. DigitalOcean’s resize documentation explains the provider constraints, including that a Droplet disk cannot be reduced.

Review the target plan’s availability in the existing region and its disk requirement. Do not offer a smaller-disk target as a routine downgrade. Additional storage can grow through the module but cannot be reduced in place; the guest filesystem may need the server administrator to extend it before applications use the added capacity.

Configure supported changes

  1. Review the source and target packages, package group and permitted service-change options.
  2. Check that the DigitalOcean account, region and target resources match the change you intend.
  3. Review the resulting price and term separately from the provider resource request.
  4. Use Blesta’s supported package/options change flow for that service.

Do not assume that editing the offering’s default plan resized existing servers. Check the affected service and its module operation.

Follow the result

Read Activity during the change and allow the existing request to finish. After completion, confirm the actual plan, memory, disk and running state, then check the application. Newly added storage can need a finishing job after the server is running.

If backups or a dedicated IP were bought as part of the change, check those separately rather than treating the main plan label as proof that every extra finished.

If the change is refused or uncertain

Read the specific reason: a smaller disk, unavailable plan, provider permission or unfinished prior operation needs diagnosis. Do not delete and recreate a live server to bypass a refused resize. Compare the billed offering, original operation result and actual server state before deciding whether another action is appropriate.

See the PD DigitalOcean Droplets Blesta guide for related tasks, or explore the module.

Table of Contents

Get your website online with PD Hosting

UK hosting, domains and support from a real team. From a first site to a full server.

Terms and Conditions  ·  Privacy Policy

PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.

PD Hosting
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.