Redis works good, but now shows Unreachable Error

  • Resolved beansbaxter

    (@beansbaxter)


    1 year, 6 months ago

    The most recent update to this plugin is now causing a Redis connection error, although Redis does and is working.

    Running v2.3.0 of this plugin, never had any problems or errors.

    Upgraded to v2.4.1 and now this error shows on the WP backend:

    Redis is unreachable: php_network_getaddresses: getaddrinfo failed: Name or service not known [tcp:///home/USER/.redis/redis.sock:0]
    • Status shows Connected
    • Filesystem shows Writable
    • But this new version added a Redis alert that now shows unreachable

    When I SSH into the server, I run this command:

    sudo -u USER -i -- wp redis enable

    And then Redis will enable within WP and works good, but it still shows the error on the WordPress backend. Screenshot:

    Here are the diagonostics:

    Status: Connected
Client: PhpRedis (v5.3.7)
Drop-in: Valid
Disabled: No
Ping: 1
Errors: []
PhpRedis: 5.3.7
Relay: Not loaded
Predis: 2.1.2
Credis: Not loaded
PHP Version: 8.0.28
Plugin Version: 2.4.1
Redis Version: 7.0.10
Multisite: No
Metrics: Enabled
Metrics recorded: 44
Filesystem: Working
Global Prefix: "wp_"
Blog Prefix: "wp_"
WP_REDIS_HOST: "/home/USER/.redis/redis.sock"
WP_REDIS_PORT: 0
WP_REDIS_DATABASE: 1
WP_REDIS_PLUGIN_PATH: "/home/USER/domains/DOMAIN.COM/public_html/wp-content/plugins/redis-cache"
WP_REDIS_PASSWORD: ????????
Global Groups: [
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache",
    "blog_meta"
]
Ignored Groups: [
    "counts",
    "plugins",
    "themes",
    "theme_json"
]
Unflushable Groups: []
Groups Types: {
    "blog-details": "global",
    "blog-id-cache": "global",
    "blog-lookup": "global",
    "global-posts": "global",
    "networks": "global",
    "rss": "global",
    "sites": "global",
    "site-details": "global",
    "site-lookup": "global",
    "site-options": "global",
    "site-transient": "global",
    "users": "global",
    "useremail": "global",
    "userlogins": "global",
    "usermeta": "global",
    "user_meta": "global",
    "userslugs": "global",
    "redis-cache": "global",
    "counts": "ignored",
    "plugins": "ignored",
    "themes": "ignored",
    "blog_meta": "global",
    "theme_json": "ignored"
}
Drop-ins: [
    "Redis Object Cache Drop-In v2.4.1 by Till Krüss"
]

    How to resolve this?

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

    (@tillkruess)

    I don’t think that config will work any longer, try this:

    WP_REDIS_PATH: "/home/USER/.redis/redis.sock"

    And remove WP_REDIS_PORT and WP_REDIS_HOST.

    Thread Starter beansbaxter

    (@beansbaxter)

    I made the changes, however that did not work. Getting this error:

    Redis is unreachable: Connection refused [tcp://127.0.0.1:6379]

    Since the older version of the plugin is working good on the same server, and because my redis.conf for the user is configured to use Port 0, I tried using WP_REDIS_PATH with WP_REDIS_PORT set to 0, but same error:

    Redis is unreachable: Connection refused [tcp://127.0.0.1:0]

    What else can I try?

    I double checked, and the plugin works great on the older version on the same server (different user). Something about this new update is causing this problem.

    Please advise.

    • This reply was modified 1 year, 6 months ago by beansbaxter.
    Thread Starter beansbaxter

    (@beansbaxter)

    Fixed the problem!

    I was not using the WP_REDIS_SCHEME variable before, when using the WP_REDIS_HOST variable.

    Changed WP_REDIS_HOST to WP_REDIS_PATH (per your instructions) and added WP_REDIS_SCHEME (set to unix) and it works good with or without the declared WP_REDIS_PORT.

    Thank you!

    Plugin Author Till Krüss

    (@tillkruess)

    ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Redis works good, but now shows Unreachable Error’ is closed to new replies.

Tags