Zambuck

I encountered a similar issue and found that in my case it related to an apparent change in behaviour of the redis container. My redis container's "Password" field was set with a value in the format "a--b--c--d" being several words separated by double-dashes. As of a recent update redis now appears to strip out the dashes entirely, resulting in my redis password actually being "abcd" instead. My fix was to update my paperless connect string to use the dash-less password and that immediately fixed the issue for me. Obviously I also could have considered changing both the redis and paperless docker parameter passwords to just not use dashes.

Just a note about a recent issue I encountered between paperless and redis. I discovered after an update to both docker images that paperless was unable to connect with redis, apparently due to a password issue. After some checking of redis I discovered that my original password, which had the format "worda--wordb--wordc--worde" was now listed in the redis.conf file as: requirepass wordawordbwordcworde I can see within the redis docker config that the "password" variable still contains the value containing double-dashes, but this latest redis update apparently strips them out. So the fix to my paperless connectivity issue was to update its credentials to the version without dashes. Not sure if this is an expected change in redis behaviour or a bug or a bug-fix but I hope it helps someone out.

Try modifying your snipe-it user similar to this, by running the command as the root MySQL user, to ensure it uses mysql password authentication: alter user snipe-it identified with mysql_native_password by 'newpassword'; Make sure the password matches what's in your snipe-it docker setup of course.