Error establishing a Redis connection?

  • Resolved pr0ject10n

    (@pr0ject10n)


    2 months, 1 week ago

    For some odd reason, in the last 7 days this plugin has started off lining my entire website and these are the messages I get.

    WordPress is unable to establish a connection to Redis. This means that the connection information in your wp-config.php file are incorrect, or that the Redis server is not reachable.

    Error establishing a Redis connection
    READONLY You can’t write against a read only replica.

    Is the correct Redis host and port set?
    Is the Redis server running?
    If you need help, please read the installation instructions.

    To disable Redis, delete the object-cache.php file in the /wp-content/ directory

    I have been deleting the object-cache file but surely there must be a better permanent solution to this. I’ve been using your plugin for months.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    2 months, 1 week ago

    READONLY You can’t write against a read only replica

    That means your replicated Redis setup has an issue. What configuration are you using?

    Thread Starter pr0ject10n

    (@pr0ject10n)

    2 months, 1 week ago

    I appreciate your quick response. I followed the instructions in this PDF (inside a cloud account) to set up my Synology server. Until last week, the Container Manager configuration worked flawlessly for months.

    Plugin Author Till Krüss

    (@tillkruess)

    2 months, 1 week ago

    Ooof, not sure about that. Did you try restarting the Redis container, or recreating it?

    Thread Starter pr0ject10n

    (@pr0ject10n)

    2 months, 1 week ago

    I’ve restarted the container again and its working for now, but I did that before and i think it only lasted 3 days before the object-cache.php solution appeared again.

    Here is a log of the errors before it stop from the Container Manager.

    16/03/2025 10:53

    1:S 16 Mar 2025 12:53:10.039 # Error condition on socket for SYNC: Connection refused

    16/03/2025 10:53

    1:S 16 Mar 2025 12:53:09.823 * MASTER <-> REPLICA sync started

    16/03/2025 10:53

    1:S 16 Mar 2025 12:53:09.823 * Connecting to MASTER 120.132.119.104:28817

    16/03/2025 10:53

    1:S 16 Mar 2025 12:53:09.093 # Error condition on socket for SYNC: Connection refused

    16/03/2025 10:53

    1:5 16 Mar 2025 12:53:08.821 * MASTER <-> REPLICA sync started

    Plugin Author Till Krüss

    (@tillkruess)

    2 months, 1 week ago

    I’d not use a replicated connection on a single Synology, just use a standalone instance it’s overkill and causing problems.

    Thread Starter pr0ject10n

    (@pr0ject10n)

    2 months, 1 week ago

    It went offline again tonight it seems to go for maybe 2 days and stops again.

    Could you explain more about ‘just use a standalone’ on a Synology server and how I can rectify the situation based on your solution without a replicated connection?

    Plugin Author Till Krüss

    (@tillkruess)

    2 months, 1 week ago

    That’s outside the scope of this plugin. I can’t help you with running and maintaining Redis Server.

    It appears you’re using a master<->replica setup where you run more than one Redis process/server, which you shouldn’t on a single machine. A single Redis node is enough and I’d suggest using supervisord or a similar tool to ensure that your Redis process will restart if there is an issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.