#I've been using the Chatwoot template for a few weeks but today I went to redeploy and it cra

22 messages · Page 1 of 1 (latest)

patent sun
#

project id: 6afa64a4-00d3-4834-8f2f-cd633469916f

atomic moatBOT
#

Project ID: 6afa64a4-00d3-4834-8f2f-cd633469916f

willow bluff
#

your redis isnt online

patent sun
#

yes, it crashed after trying to run chatwoot, I don't know if it's related

willow bluff
#

chatwood needs redis to run

patent sun
#

I will turn on redis again to test

willow bluff
#

you also have multiple services connected to the same redis and postgres db

#

and whats app bots are not allowed...

patent sun
#

It's not a WhatsApp bot, it's to connect to Chatwoot

willow bluff
#

okay cool

patent sun
#

It worked now, I don't know how it was working before, thanks. I'm using other redis instances now

#

I don't see any problem with Postgres, there are several DBs within that instance

willow bluff
#

fair enough, all good then!

patent sun
#

@willow bluff now n8n no longer connects to redis

willow bluff
#

is redis active?

patent sun
#

yes

willow bluff
#

are all the services using a diffrent database? eg /0 /1 and so on

patent sun
#

yes and I created a new redis instance just for n8n

willow bluff
#

n8n uses ioredis internally and can't connect to redis over ipv6 without family set to 6, but n8n does not provide a way to set that so you would need to have n8n connect to redis over the public network

patent sun
#

It's true lol, I had forgotten about that