Skip to main content

Redis on shared hosting server

Comments

4 comments

  • cPRex Jurassic Moderator

    Hey hey!  While this isn't directly related to cPanel, it looks like having a unique ID is a requirement:

    https://chemicloud.com/kb/article/redis-object-cache-in-wordpress/

    "Please keep in mind that if you have multiple websites using Redis Object Cache, you need to specify a unique number in the Redis Database ID field for each individual website."

    0
  • Benito

    Hi Rex, thank you. It's exactly what I was asking about. I don't know if each cPanel user has their own Redis instance or if it is the same one shared for the entire server.

    If it's the latter and both clients use the same ID that could be a problem.

    I thought you guys would know how to answer this.

    0
  • cPRex Jurassic Moderator

    I'm not completely sure what additional details you need.  When you configure the plugin, do you not have to enter the DB ID information manually?  That would ensure there are no duplicates.  But no, I don't have a more automated way of ensuring that duplication doesn't happen.

    It's important to note that by default, cPanel only provides support for Redis in a container environment, which would be limited to just one specific cPanel user.  Details on that can be found here: https://docs.cpanel.net/ea4/containers/redis-via-containers/

    0
  • Benito

    The ID number is entered manually by each user. I think they are 0 to 16 according to the default redis configuration. That's why I was interested in knowing if having this installed could generate some data crossing between all the users of our servers.

    Since we do not use Ubuntu, Almalinux or Rocky Linux, we do not use containers and we were able to install REDIS via yum and easyapache following this thread https://support.cpanel.net/hc/en-us/community/posts/19142380276759-Recommended-way-to -install-redis-on-WHM-CentOS-7-.

    I suppose that if I don't have containers, the user data could cross over the same redis ID.

    0

Please sign in to leave a comment.