#Redis Object Cache Wordpress -Redis is unreachable: Connection refused [tcp://127.0.0.1:6379]
20 messages · Page 1 of 1 (latest)
Sounds like you don't have redis running on your client's local host at port 6379?
When I Ping Via SSH I Get Pong Response
I am not someone with high knowledge and the hosting company said that this is not their field.
what command are you running from ssh?
Sorry Not SSH , with Terminal
what do you get if you run ps -ef | grep wordpress?
at the end of the day it's probably an ssh terminal running on a thin client so you're likely not wrong.
It was previously hosted on Shared Hosting. I asked them to move it to a VPS server. They told me they had moved it.
Didn't they carry it?
I'm honestly not overly familiar with wordpress deployments - do you see anything if you do:
ls /var/www
or
ls /srv/www
try:
find /var/www -type f -name wp-config.php
ok, so it doesn't sound like wordpress is installed on the same machine as Redis
Then I will meet with the Technical Team again and report the development here.
So what the error you are seeing is referring to:
Connection refused 127.0.0.1 6379
This is a really common TCP error, it means that the host and socket that your client (in this case your wordpress instance) is talking to doesn't have a TCP server sitting on the other side of it. 127.0.0.1 is the ipaddress of the loopback interface for localhost, so wordpress is trying to reach Redis on the same server it's deployed to, nothing is there listening, so the connection dies. Now, we know that this server HAS redis on it on port 6379 (you were able to verify it by running redis-cli ping , localhost:6379 are the defaults).
Now, I am not familiar with wordpress, but it doesn't sound like it's running on that server, so you will need to go to your wordpress server and reconfigure it to point at the vps that redis is running on.