PD DigitalOcean Droplets creates and manages servers in your own DigitalOcean account. Add that account connection before preparing a Blesta package, then check that the intended offering uses it.

Prepare the token

In DigitalOcean’s API settings, create a dedicated personal access token for this integration. Review the expiry and store a replacement plan. An expired or revoked token prevents new management requests even though existing servers can keep running.

The module needs write permissions for the resources it manages, not just permission to list them. Its account guide describes Full Access and Custom Scopes for droplets, storage, firewalls, reserved IPs, SSH keys, tags, snapshots and projects, plus the necessary account/catalogue/monitoring reads. Full Access is broader; use a custom set only after checking the operations and dependencies you need. DigitalOcean publishes the current token scope definitions.

Save the connection

1. Open Settings → Company → Modules and choose Manage beside installed PD DigitalOcean Droplets.
2. Add an account with a recognisable Account name and the token in API token.
3. Choose Save account. The other provider fields are not used for this connection.
4. Open PD Modules → DigitalOcean Droplets and run Test Connection.
5. Select this account when configuring the package.

The connection test is read-only and does not create a Droplet. A successful test does not establish that a token can create or change every resource used by the offering.

Read failures accurately

For 401, check whether the token is invalid, expired or revoked. For an action-specific 403, check the permission needed by that action. A read-only token can pass the connection test but fail creation. A successful read is not a reason to repeatedly retry an unsuccessful write.

For a timeout, check the billing server’s outbound HTTPS access to DigitalOcean with your server administrator. For an account-limit error, review the actual provider limit rather than changing the package’s plan at random.

Rotate without discarding the working connection

Create a replacement token with the intended permissions, update the saved connection, and test it before retiring the old token. Review the original failing operation separately if it needed write access. Keep tokens out of tickets and screenshots; provide the redacted error and connection name when asking for help.

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