Magento 2 Redis Errors - Separate Redis instance

Job ID: 32503392

Budget: $15 – $25 USD

Magento 2 Redis Errors - Separate manicaa.com / karibaa.com Redis instance

Apply only if you are an expert at fixing Redis

We need help with our Magento 2 Redis on Manicaa & Karibaa



We have 2 Magento 2 stores on the same server and the problem is they are using the same redis instance which is causing issues with redis & memory. We need help with splitting redis into two different instances, one for each store so that the stores do not share redis. and check configuration or configure varnish well.

while redis saves this cache - it doesn’t accept connections

[2021-12-23 15:05:37] main.CRITICAL: Connection to Redis 127.0.0.1:6379 failed after 1 failures.Last Error : (1) read error on connection to 127.0.0.1:6379 [] []
[2021-12-23 15:05:37] main.CRITICAL: Connection to Redis 127.0.0.1:6379 failed after 1 failures.Last Error : (1) read error on connection to 127.0.0.1:6379 [] []
[2021-12-23 15:05:37] main.CRITICAL: Connection to Redis 127.0.0.1:6379 failed after 1 failures.Last Error : (1) read error on connection to 127.0.0.1:6379 [] []
[2021-12-23 15:05:37] main.CRITICAL: Connection to Redis 127.0.0.1:6379 failed after 1 failures.Last Error : (1) read error on connection to 127.0.0.1:6379 [] []
Related categories: Redis Varnish Cache Magento 2