Issues connecting to valkey using private connection string

Question

I have a node server running on app platform connected to a vpc, from which I’m trying to connect to valkey using the ioredis package

i also have a managed valkey instance in the same region as the node server

connecting using the valkey public string provided in the digital ocean valkey dashboard works absolutely fine with no issues connecting. However when I substitute the string for the private one the server fails to connect.

I Have tried attaching the database to the app in the app platform settings. But this doesn’t work either. I have also tried adding the app as a trusted source in the valkey setting but with no luck also.

maybe perhaps there’s an additional step or configuration I’m missing? If anyone could please help.

many thanks

979a231aa86341ffa7ff72874e2f5d · Answer

Just in case it helps anyone else I’ll answer my own question having done some digging and testing its only the build step that was failing as this happens I can only assume in a sandboxed environment outside the box hence not being able to connect. during my build as files are being imported my redis connection was being made. I instead switched to a function which returns the connection when its called. i also added variables which are truthy during the build step so we can avoid certain functions being called during build.

alexdo · Answer

Heya, @979a231aa86341ffa7ff72874e2f5d Private Valkey on DO usually only works if both resources are on the same VPC network, not just the same region. App Platform’s VPC connector needs to be enabled correctly, and your app has to use the internal host exactly as provided, usually on the private network endpoint without forcing TLS unless that private endpoint specifically requires it. A common issue is using the private connection string with rediss:// when the private endpoint may expect redis://, or vice versa depending on config. Also make sure your app component is actually deployed with the VPC attachment after changes, since settings sometimes don’t apply until redeploy. If public works but private doesn’t, it’s usually VPC routing or DNS resolution rather than credentials. Double check that the App Platform service and Valkey database are in the same project/VPC context, then test DNS resolution of the private hostname from inside the app container. Regards

a536bfb7dc9d4306afbe33daff2b9c · Answer

Are your App Platform app and the Valkey instance attached to the same VPC? Also, what’s the exact ioredis error when using the private endpoint? That will help determine whether it’s a DNS, networking, or authentication issue.

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

Issues connecting to valkey using private connection string

Report this

Issues connecting to valkey using private connection string