Testing needs to use a system which is configured to use Redis for (a) user session, and (b) at least one MUC cache, as per these instructions: https://docs.moodle.org/400/en/Redis_cache_store https://docs.moodle.org/400/en/Session_handling#Redis_session_driver There should be no difference in behaviour, so please just: Confirm you can successfully log into Moodle Under Site administration > Development > Debugging , turn on the Performance info option (perfdebug). Click around a few pages and confirm you are still logged in. On a page which exercises at least one Redis MUC cache and where data should be coming from the cache, look at the performance info at the bottom of the screen and confirm there is a cache hit (H) for the Redis cache; i.e. the cache appears working. Optionally we can do extra testing to confirm that the ping commands are not happening. There are 2 different ways to do this: 1) If you have CLI access to Redis: a. Run 'info commandstats' and look for the number of calls to ping (note - if the ping line is absent it means there weren't any, you can manually type 'ping' first if you want it to show up): > info commandstats # Commandstats ... cmdstat_ping:calls=1,usec=1,usec_per_call=1.00 ... b. Make some Moodle web page requests c. Run 'info commandstats' again and confirm the number of ping commands is still the same 2) If you have profiling enabled on your Moodle server a. View a course page with profiling on (e.g. add &PROFILEME=1 to the end of the URL, if you have selective profiling enabled). b. Look at the profiling result by going to Site administration / Development / Profiling runs , click on the date of the profiling run, then click View profiling details c. In the search box at top right, type 'redis'. Verify that you see several commands starting 'Redis::' including 'Redis::connect', but no 'Redis::ping'.