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

10 months ago

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

0 Replies

10 months ago

your redis isnt online


10 months ago

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


10 months ago

chatwood needs redis to run


10 months ago

I will turn on redis again to test


10 months ago

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


10 months ago

and whats app bots are not allowed…


10 months ago

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


10 months ago

okay cool


10 months ago

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


10 months ago

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


10 months ago

1273015731021414400


10 months ago

fair enough, all good then!


10 months ago

@Brody now n8n no longer connects to redis


10 months ago

is redis active?


10 months ago

yes


10 months ago

1273029054957621200


10 months ago

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


10 months ago

yes and I created a new redis instance just for n8n


10 months ago

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


10 months ago

It's true lol, I had forgotten about that


10 months ago

despite how friendly railway is there is no eliminating all the gotchas that comes with the ability to deploy nearly any software