In the past, I've tried using #redis sentinel for this #mastodon instance. But looks like there is a long standing bug on rubby with redis sentinel.
I don't know if it has been resolved by now. But I think I found a quick resolve for this problem, using a redis proxy whose support sentinel. And one of my candidate is enriclluelles's redis-sentinel-proxy https://github.com/enriclluelles/redis-sentinel-proxy
Will try it soon. There is 3rd party container image at https://hub.docker.com/r/patrickdk/redis-sentinel-proxy

If you're setting up a new server on the Fediverse, it's usually best to use a fresh domain or subdomain that has never been used by any previous Fedi servers.
If a new server recycles the subdomain or domain from a defunct server, it may sometimes cause technical problems when trying to connect to other Fediverse servers.
More info about this and how to avoid problems at:
You can also create a new subdomain on an existing domain to avoid problems.
RE: https://neuromatch.social/@jonny/116344579209407001
#FediBlock @tuban_muzuru (and their other account @tuban_muzuru), see below:

Anybody know anything about vebinet<dot>com? stella_reed from there seems to be a bot-like creature. Joined mar. 22. Earliest posts read like AI free verse. Goes on with demoralising, (partly unsourced) media-quotes .
Fediverse admins,
You can get a headstart on moderating your server by using ready-made server blocklists. There are many different lists to choose from, pick the one that suits your server's needs the best.
There's a guide for admins about using ready-made server blocklists on Mastodon here:
➡️ https://fedi.tips/importing-ready-made-server-blocklists-on-mastodon
There's a good roundup of many different blocklists by @oli at:
➡️ https://writer.oliphant.social/oliphant/the-oliphant-social-blocklist
9 more Meta Platforms /16 subnets blocked for scraping my Fedi sites.
Updated the #ThreatFeed and applied to my networking and web systems.