Hosted Redis and Droplet: No connection is available to service this operation

Good day

I have a droplet for which I recently introduced a firewall and I have a hosted redis server on digital ocean.

Lately I started getting and error: No connection is available to service this operation: EVAL; It was not possible to connect to the redis server(s)

My first thought might be that its the firewall but to be honest, I actually had a the firewall for a while before this error occurred but might be related. I did however try and set the outbound port to that of my redis server without it doing anything.

After I started seeing this error, I set the eviction policy to allkeys-lru on my redis server and also added security so only my droplet and home(dev) pc can connect.

Locally in my Dev env I am not getting any errors. only from my two .Net apps on my droplet.

I am not sure what might be causing this?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.


As you had the Firewall in place long before you were seeing the problem, it could be that the Redis instance is having some issues and might be crashing.

I could suggest checking your server logs to see if this is the case. Also, you could take a look at the monitoring graphs via your DigitalOcean control panel and see if there are any spikes during the times when you see the timeouts.

Another thing you could check is the Redis service itself and check if it has been restarted around the time of your last timeout:

systemctl status redis

Regards, Bobby