Hi,

I’m trying to expose a Redis service over the web using a droplet, for now I’m trying to get it to work regardless of any security features.

I’ve followed this tutorial, and everything does work fine locally.
When trying to expose the service, I :

  • Replaced bind 127.0.0.1 with bind 0.0.0.0 in the /etc/redis/redis.conf file, the line does not have a leading # nor space,
  • Replaced protected-mode yes with protected-mode no in this same file,
  • Allowed all traffic to port 6379 using ufw allow 6379 and ufw allow 6379/tcp

But I can’t get it to work. When checking internally using systemctl status redis I see CGroup: [...] /usr/local/bin/redis-server 127.0.0.1 and using redis-cli will show 127.0.0.1>. I thus think that Redis doesn’t correctly bind to 0.0.0.0 and am wondering why.

Would you guys know of any possible conflicts or errors ?

Thanks

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.

×
2 answers

Nevermind this question, this only resulted in the fact that the redis.conf file has two lines showing bind 127.0.0.1 and I only had noticed one of these two…

Hello here is the answer, I followed every step and just one thing we are missing here. Its not using your edited conf file, you need to pass path explicitly.

if you are using Linux try this for starting:
./redis-server /path/to/redis-stable/redis.conf

Submit an Answer