Connect the DigitalOcean account that will own your customers’ managed database clusters. Saving a credential and successfully creating a database are separate checks.

Prepare the account token

Create a personal access token under Account → API → Tokens in DigitalOcean. Copy it when shown and record its expiry privately. The module documentation describes Full Access; for Custom Scopes, use DigitalOcean’s current scope reference to cover account reads and the database operations you intend to provide, including their required scopes. A read-only token cannot provision or change databases.

Do not put the token in a product description, screenshot or support message. DigitalOcean explains token creation and permissions in its personal access token guide.

Save it in Blesta

Open Settings → Company → Modules, find PD DigitalOcean PostgreSQL under Installed and choose Manage. Add the Account name and API token; leave fields marked Not used for DigitalOcean empty. Save the account and select it on the intended package. When editing a stored account, a blank token box keeps its existing token.

Check what Test Connection proves

Open PD Modules → DigitalOcean PostgreSQL → Settings and run Test Connection. This module-level button checks the first active configured account through an account read. It does not test every account, create a cluster or prove that database write permissions and capacity are available.

If you use several accounts, verify which account the target package and service actually use. A successful first-account test does not validate a different selected account.

Resolve a failed connection

Review a 401 for a wrong, expired or revoked token; review a 403 against the exact operation and its permissions. An account test that passes while an order fails does not establish the cause: region, plan, account limits and provider availability also matter. Check outbound HTTPS access if the billing server cannot reach DigitalOcean.

When rotating credentials, save the replacement, check the intended account and required operations, then revoke the old token after verification. A passing account read alone does not prove complete continuity. Keep an expiry reminder.

See the PD DigitalOcean PostgreSQL Blesta guide for related setup, or explore PD DigitalOcean PostgreSQL.