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

2 years ago

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

21 Replies

2 years ago

your redis isnt online


2 years ago

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


2 years ago

chatwood needs redis to run


2 years ago

I will turn on redis again to test


2 years ago

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


2 years ago

and whats app bots are not allowed...


2 years ago

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


2 years ago

okay cool


2 years ago

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


2 years ago

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


2 years ago

1273015731021414440


2 years ago

fair enough, all good then!


2 years ago

@Brody now n8n no longer connects to redis


2 years ago

is redis active?


2 years ago

yes


2 years ago

1273029054957621340


2 years ago

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


2 years ago

yes and I created a new redis instance just for n8n


2 years 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


2 years ago

It's true lol, I had forgotten about that


2 years ago

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...