Include a dedicated DigitalOcean IP in a Blesta package
Use the Droplets offering’s Dedicated IP setting when the service should receive a DigitalOcean reserved IP. Configure the default and any checkout choice consistently, then verify the address on the provisioned service.
Configure new services
- Open Packages → Packages → your package for the PD DigitalOcean Droplets offering.
- Review the intended account, region and plan.
- Enable Dedicated IP if it should be included by default and save.
- If customers can buy it as an option, review Dedicated IP under the generated configurable options and its visibility/price.
- Check that the order form and service description explain whether the address is included or selected separately.
A customer option can override the saved default. Editing the default is not evidence that an existing running server received a reserved IP.
Verify the actual service
When an intentionally provisioned service is ready, allow its finishing job to complete the reserved-IP assignment. Read its server details and Connection details, and review Activity for that networking step.
A reserved address and a DNS record are different resources. The customer still needs to point the intended domain or external application at the correct address and configure the service listening on the server.
Consider changes and cancellation
A dedicated IP can be added through a supported service-option change where offered. Recheck the actual assignment after the operation rather than relying only on the billed option.
The module’s teardown removes the dedicated IP it managed when the service is terminated/cancelled. Do not assume a cancelled server remains a destination for a working domain. Plan DNS or external-service changes before ending the server when those records must keep serving traffic.
If assignment is incomplete
Check the purchased selection, service state and the networking Activity result. Review the provider account permission or quota named by an error. A provider request that is still pending is not a reason to create another server.
Compare the existing reserved address and assignment with the intended service using your own DigitalOcean access. Preserve the original request time and networking result. Do not release a working reserved address merely to test whether another allocation would succeed.
See the PD DigitalOcean Droplets Blesta guide for related tasks, or explore the module.