Providers

DigitalOcean Managed Caching

Valkey-backed DO Databases — Overview Connection Details, trusted sources, TLS-required high port.

DigitalOcean's managed Redis offering moved to Valkey (Managed Caching) after Aiven stepped back from Redis. Wire protocol unchanged — drivers.store.kv stays redis.

The one rule

Databases → cluster → Overview → Connection Details. Copy the rediss:// URI (public or private). Add the client to Trusted Sources or you get connection refused.

Find credentials (current control panel)

  1. cloud.digitalocean.com/databases → click the Valkey / Caching cluster.
  2. OverviewConnection Details:
    • Toggle Public network vs Private network (VPC)
    • Copy host, port, user, password, or the assembled connection string
  3. Password is hidden until you reveal/copy it in that panel.
  4. Network Access / trusted sources: add app Droplet, App Platform app, or VPC CIDR (from Overview VPC Network) before connecting.
process env
REDIS_URL=rediss://default:PASSWORD@db-valkey-nyc1-….db.ondigitalocean.com:25061

Port is a random high port from Connection Details — not 6379. TLS is required; there is no plaintext option.

Production guidance

TopicGuidance
EngineValkey on new clusters; older “Managed Redis” capped / unsupported past Redis 7.2
TLSAlways — use rediss://
Trusted sourcesHard firewall — missing entry ⇒ refused even with correct password
VPCPrefer private connection string + VPC CIDR as a single trusted source

Standalone Upstash-on-DigitalOcean marketplace listings are a different, deprecated product — not this Databases service.

Real gotcha — trusted sources

Correct REDIS_URL from a laptop not in Trusted Sources fails with connection refused. Add your IP (or use a Droplet already allowed / VPC CIDR) under Network Access.

Troubleshooting

Learn more

Next

On this page