Redis Object Cache plugin shows as Not connected

Follow

Comments

9 comments

  • Avatar
    Neil Elver

    Thanks for this detailed workaround for the WordPress plugin. It seems the plugin developer has relaxed their requirement, so it now works even with the older PHPRedis 3. But I still prefer to keep my installations on the latest 5.1 for performance reasons. 

    The challenge, however, is that with each incremental PHP patch release auto-applied to our Plesk farm I need to redo the above steps, as the updated PHPRedis gets overwritten as part of the upgrade. With the 3.0 version being released Jun 10, 2016 is there any plan to get the Plesk PHP updater to use a new version? I'd rather not have to build a plan around trying to cron-job update PHPRedis to keep it up to date despite Plesk regularly rolling it back.  

    1
    Comment actions Permalink
  • Avatar
    Pavel Rozental

    Hello Neil Elver, 

    Currently we do not have an ETA  when bug PPP-45378 is fixed.

    0
    Comment actions Permalink
  • Avatar
    Michel

    Almost 5 months have passed is PPP-45378 finally resolved?
    Or do you really have to redo all those steps again as Neil mentioned?

    If not fixed, than please create a work-around as this will take to much time for the customers with (newer) Redis installed (server/client). TY.

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Michel!

    This should be resolved since Plesk 18.0.29.

    PHPredis was updated to 5.3.0.

    The article will be updated too.

    0
    Comment actions Permalink
  • Avatar
    Michel

    Hi Ivan,

    Yeah, I noticed this myself earlier this week. So we do not need to upgrade PHP anymore through PECL, right?

    And what happens if I did anyways? As it did say it upgraded things. Would it harm or change anything in future upgrades by Plesk or will it revert just back to PHPredis 5.3.0 as Plesk supplies?

    Thanks.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Michel

    Some time will be required to prepare an answer.

    Expect an update in the ticket.

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy (Edited )

    Hi Michel

     

    I updated redis by following this article on  Plesk 18.0.20.

    After that, I upgraded to 18.0.29 and no issues were shown in Redis.

    That being said, you do not need to do anything after upgrading to Plesk 18.0.29.

    0
    Comment actions Permalink
  • Avatar
    Neil

    I am still getting this problem. Configured properly in wordpress config. 

    In docker I might be missing some parameters not sure, but I am using the most used image out of all listed. 

    I have set it up on Wordpress many times. However with this server I am getting:

    Status: Not connected
    Client: PhpRedis (v5.3.2)
    Drop-in: Valid
    Disabled: No
    Filesystem: Working
    Ping:
    Connection Exception: Connection refused (RedisException)
    Errors: [
    "Connection refused"
    ]

    Do I need to open a port or something?

    The docker image container is running fine.  Its all as you would expect but I cannot work out why it wont connect. 

    PHP settings has Redius checked too. 

     

    0
    Comment actions Permalink
  • Avatar
    Ekaterina Babenko

    Hello,
    Try to open port configured during setting up Redis:
    https://support.plesk.com/hc/en-us/articles/115001078014-How-to-manage-local-firewall-rules-using-Plesk-Firewall-on-Linux

    If it does not help submit request to support since investigation is required;
    https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support- 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request