DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
abdelrahmanahmed605
TRIALOP

a year ago

Use case: I am trying to deploy the backend server from an open-source project. One of the server requirements is a Redis host. I deployed a Redis project in the same environment and followed the guide (adding the REDISHOST, REDISUSER, REDISPORT, REDISPASSWORD, REDIS_URL environment variables). The build works but my deploy logs keep showing the error getaddrinfo ENOTFOUND redis.railway.internal. I tried adding a sleep 3 to my start command and that did not work. I also tried adding ?family=0 to my redis_url environment variable but that did not work. What is causing this deploy log issue and how can I fix it?

For reference if needed: the open source project is https://github.com/twentyhq/twenty and the backend server is in the directorypackages/twenty-server.

This is the website where they mention the required environment variables for self hosting https://twenty.com/developers/section/self-hosting/self-hosting-var

12 Replies

abdelrahmanahmed605
TRIALOP

a year ago

1f5270ce-3093-4e79-a5ae-cb50643f41a9


a year ago

why is redis needed here?


abdelrahmanahmed605
TRIALOP

a year ago

The backend server requires a cache storage in the code implementation. Without it I get Error: connect ECONNREFUSED 127.0.0.1:6379 during my build


a year ago

are you using the twenty template? -


abdelrahmanahmed605
TRIALOP

a year ago

No I am not using the template, because I am deploying the frontend elsewhere separately and using an already existing postgres database


abdelrahmanahmed605
TRIALOP

a year ago

So I am just trying to deploy the twent-server only


a year ago

i would recommend using the template


abdelrahmanahmed605
TRIALOP

a year ago

It might be difficult since the rest of the services are deployed elsewhere.

I'm curious though why not using the template would give me the error I mentioned since I have a redis server deployed


a year ago

haven't looked into it, but the template likely works without issues so thats going to be my recommendation


abdelrahmanahmed605
TRIALOP

a year ago

I tried deploying the template and got the error ``` ERROR [ExceptionHandler] connect ECONNREFUSED 127.0.0.1:6379

Error: connect ECONNREFUSED 127.0.0.1:6379

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)```

Is the template supposed to work out of the box?


a year ago

i would hope so


a year ago

i see you already let the maintainer know, so i will close out this thread and let the template maintainer assist you.


Loading...