Nextcloud can't connect to local redis (via socket) anymore after ncp update to v1.53.1

I’ve been running ncp for quite a while now. Some weeks ago, nextcould stopped working with an redis connection error, I guess after an update, I think it was after update to ncp v1.53.1. Now I updated to v1.53.2 and still have the same issue:

❯ ncc maintenance:mode --off
An unhandled exception has been thrown:
RedisException: Permission denied in /var/www/nextcloud/lib/private/RedisFactory.php:137
Stack trace:
#0 /var/www/nextcloud/lib/private/RedisFactory.php(137): Redis->pconnect()

my config.php is:

<?php
$CONFIG = array (
...
 'redis' => 
  array (
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'timeout' => 0.0,
    'password' => 'mypw',
  ),

when I connect to redis via cli as user www-data with the PW from config.php, it works. I also checked permissions of /var/run/redis/redis.sock and they look fine to me.

❯ sudo -E -u www-data redis-cli -s /var/run/redis/redis.sock -a mypw PING
PONG

The system info at https://nextcloudpi.local:4443/ reports that only the HPB is down.

NextcloudPi version	v1.53.2
NextcloudPi image	NextCloudPi_RaspberryPi_v1.50.3.img
OS	Debian GNU/Linux 11. 5.10.92-v8+ (aarch64)
automount	yes
USB devices	sda
datadir	/media/myCloudDrive/ncdata/data
data in SD	no
data filesystem	btrfs
data disk usage	518G/1.9T
rootfs usage	9.5G/29G
swapfile	/var/swap
dbdir	/media/myCloudDrive/ncdatabase
Nextcloud check	ok
Nextcloud version	27.1.6.2
HTTPD service	up
PHP service	up
MariaDB service	up
Redis service	up
HPB service	down
Postfix service	up
Internet check	ok

Any suggestion?

As a temp solution, I switched from redis to APCu and my nextcloud is up again. Without redis for file locking.

The docs say that APCu is faster at local caching than Redis and Redis should be used for file locking, if the server has enough memory. So maybe, I keep APCu - not sure if this would cause issues on future ncp updates. Guess so.

But nevertheless, I’d like to have my redis connection back :confused: