Iāve ran NC for a good few months (migrated from OC) and ran it with redis from the get-go. Today i notice iām having an issue with my NC container and after a little bit of diag, i see it appears to be a redis issue (output from nextcloud.log)
{āreqIdā:ānUakFPBhkkgfizv218pGā,ālevelā:3,ātimeā:ā2021-01-06T10:35:37+00:00ā,āremoteAddrā:ā192.168.1.87ā,āuserā:āāā,āappā:āindexā,āmethodā:āGETā,āurlā:ā/nextcloud/index.phpā,āmessageā:{āExceptionā:āRedisExceptionā,āMessageā:āERR AUTH called without any password configured for the default user. Are you sure your configuration is correct?āā¦
so i stop, remove and start a fresh container of both redis and NC without āāenv REDIS_HOST=ā:
podman run -d
ālabel āio.containers.autoupdate=imageā
āname nextcloud
āpublish 8085:80
āvolume /mnt/nextcloud/:/var/www/html
āenv MYSQL_HOST=10.88.0.1
āenv MYSQL_DATABASE=nextcloud
āenv MYSQL_USER=nextcloud
āenv MYSQL_PASSWORD=REMOVED
āenv NEXTCLOUD_ADMIN_USER=REMOVED
āenv NEXTCLOUD_ADMIN_PASSWORD=REMOVED
āenv NEXTCLOUD_TRUSTED_DOMAINS=REMOVED
āenv APACHE_DISABLE_REWRITE_IP=1
nextcloud
but it still seems to be needing redis with the above nextcloud.log error. Is there something in the DB that i need to kill thats referencing redis? i did have some issues with my home server with my volume side going offline but sql remained online at the time. thats the only issue i can think of as a possible cause.
i use the docker _/redis release that explicitly disables password usage by default so why nextcloud is seemingly having issues with redis auth, iāve no idea.
fwiw, redis is configured as:
podman run -d
ālabel āio.containers.autoupdate=imageā
āname redis
āpublish 6379:6379
āhostname redis
ārestart=on-failure:5
redis
How do i fix the redis auth issue? iād prefer to keep using redis primarily for file lock handling but it seems even under testing the NC docker image seems to continue to use it even when not defined in the config.
NC is currently offline so any help would be useful 