Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’m trying to set up an example app with a Node.js Express server, a managed DO Redis db, and a Node.js worker.
I’m using the server.js and worker.js code from Heroku’s “node-workers-example”. I’m deploying by pushing containers to a DO Container Registry.
I got this app working locally with docker-compose, using the docker hub’s official redis image as the db, but I can’t get it to connect to my managed DO redis db.
(The code linked above doesn’t catch errors, but if I catch them, I see this):
Error: read ECONNRESET
MaxRetriesPerRequestError: Reached the max retries per request limit (which is 20). Refer to "maxRetriesPerRequest" option for details.
The app itself appears to just hang and timeout when I post to the /job endpoint and try to make the first connection do the DB.
Things I’ve checked:
DATABASE_URL, which I renamed to REDIS_URL to work with this code.bull, which uses ioredis under the hood to connect. I thought it might be a problem with TLS, but I was able to connect locally using ioredis with the same connection string (DATABASE_URL, which is rediss://default:<password, etc.>I don’t know if the problem is specific to Node Bull here, but I don’t know how to begin debugging it beyond just logging as much as I can to the JS console.
lwmeozrcbh
d1dd3d9538cc4d06b53e6d1d338d3f
50ff4e4b3c6c4999a12403b1ecda95
a6309a057c3f4cb38fb2e7feb67236
72e571841e7f4a6881090a2f3e93c0
7ce6bf277bff4d429ba493dd750e35
57a72a98162f46a5a5cd04d9b
Thomas Brocken
11575c6d695643cdb40ad47d0f1aea
tez.saad