Use PD DigitalOcean Databases to allow the application servers that should connect to a customer’s database. Its client control manages address rules, not every kind of provider-side trusted resource.

Check access before editing

Open the intended service’s Firewall page. Enable Client: Firewall on the product. Review the application’s actual connecting IPv4 address or CIDR range, including any outbound NAT, instead of assuming its website address or your browser’s address is correct.

Save the intended address list

1. Read the existing address entries before making changes.
2. Add the required IPv4 addresses or CIDR ranges and retain every existing address that still needs access.
3. Remove an old address only after checking its application no longer needs it.
4. Save the list, reload it and test the intended application connection after the provider applies the update.

An invalid non-empty address refuses the change. IPv6 rules are not supported by this control. The update replaces the client-managed address list while retaining provider-side rules of other types; it is not an additive update to only the line you just edited.

Understand an empty list

DigitalOcean treats a genuinely empty trusted-sources configuration as unrestricted by trusted source. Clearing all address entries is therefore not a way to block all access. Other provider-side trusted resource rules can still exist even when this address-only view is empty.

An empty display can also result from a failed read. It does not prove the firewall has no rules. Do not save a replacement based solely on an unexpectedly empty screen; establish the current configuration first.

If an update fails

Trusted sources cannot be changed through this control while the service is suspended. A successful save records the provider update request; verify the resulting list and the real application connection rather than assuming a precise propagation time. If the result is uncertain, establish the current rules before repeating a save. Keep database credentials out of shared screenshots.

See the PD DigitalOcean Databases WHMCS guide for related setup, or explore PD DigitalOcean Databases.