abed3k
abed3k
Explore posts from servers
RRailway
Created by abed3k on 10/2/2024 in #✋|help
DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
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)
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?
14 replies
RRailway
Created by abed3k on 10/2/2024 in #✋|help
DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
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
14 replies
RRailway
Created by abed3k on 10/2/2024 in #✋|help
DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
So I am just trying to deploy the twent-server only
14 replies
RRailway
Created by abed3k on 10/2/2024 in #✋|help
DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
No I am not using the template, because I am deploying the frontend elsewhere separately and using an already existing postgres database
14 replies
RRailway
Created by abed3k on 10/2/2024 in #✋|help
DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
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
14 replies
RRailway
Created by abed3k on 10/2/2024 in #✋|help
DEPLOY logs showing Error: getaddrinfo ENOTFOUND redis.railway.internal
1f5270ce-3093-4e79-a5ae-cb50643f41a9
14 replies