Find the MongoDB service’s connection details in PD DigitalOcean MongoDB, then configure a compatible MongoDB client with the correct authentication and TLS settings.

Open the service connection window

Open the intended client service’s Overview page and choose View connection details once the cluster is ready. Enable Client: Connection details on the product. Copy its host, username and database where supplied; reveal the masked password with Show only when needed.

Keep credentials and any URI containing a password out of screenshots, public posts and support messages. Use the details for this service rather than values copied from another MongoDB cluster.

Keep TLS and authentication settings together

The module’s MongoDB example uses mongodb+srv, tls=true and authSource=admin. The database your application opens and the database used to authenticate are separate settings. Changing the application database does not imply that the authentication source should change with it.

SRV connection syntax lets a compatible client discover the cluster’s hosts through DNS. Do not turn that URI into a single-node direct connection by guessing an address or inserting a port into its SRV hostname. If your client requires individual connection fields, use that client’s documented configuration and confirm any missing settings against the intended cluster.

Supply the service password through the client’s supported credential setting or prompt. Let the client handle any required URI encoding instead of pasting an unescaped password into a connection string.

Trust the cluster certificate

Use Download CA certificate when offered and configure your client’s CA trust as required. Keep TLS and certificate/hostname verification enabled; do not disable verification to bypass an error.

DigitalOcean’s MongoDB connection guide explains provider-side connection formats. Those additional provider screens do not imply that PD DigitalOcean MongoDB exposes user creation, database administration or every connection setting as a client-area control.

Diagnose a failed connection

Check the service’s state, allowed source IPv4 address, current username/password, authentication source, TLS trust and SRV-capable DNS resolution. A Running banner or stored endpoint is not a fresh application connection test; failed provider reads can leave stored values visible.

Review the error alongside the client software and version. Do not recreate the database, reset the password repeatedly or send a complete credential-bearing URI to diagnose an uncertain connection failure.

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