Unable to connect to redis
Trying to move the redis instance to the new region, however am unable to connect to it on the UI as well as CLI. Any pointers as to how to resolve this?
27 Replies
Project ID:
34201471-b3bb-47a4-84b4-5e87c08ca75634201471-b3bb-47a4-84b4-5e87c08ca756
deployment logs please https://bookmarklets.up.railway.app/log-downloader/
Oh wait I guess that explains, but then how do I deploy it?
uh, thats not ideal
does it have any variables?
nope, none thats alred
altered*
so yes all the variables are there?
RAILWAY_RUN_AS_ROOT=true
RAILWAY_RUN_UID=0
REDISHOST=${{RAILWAY_TCP_PROXY_DOMAIN}}
REDISPASSWORD=${{REDIS_PASSWORD}}
REDISPORT=${{RAILWAY_TCP_PROXY_PORT}}
REDISUSER=default
REDIS_PASSWORD=<REDACTED>
REDIS_PRIVATE_URL=redis://default:${{REDIS_PASSWORD}}@${{RAILWAY_PRIVATE_DOMAIN}}:6379
REDIS_URL=redis://default:${{REDIS_PASSWORD}}@${{RAILWAY_TCP_PROXY_DOMAIN}}:${{RAILWAY_TCP_PROXY_PORT}}
this is the env
does it have a source?
could you elaborate?
looks like it
@Melissa @Angelo - even services with images sometimes fail to deploy, the force deploy button would be great in this situation
but for now, youd have to remove the image and add it back
Literally was just talking about this
gotcha, lemme try that
angelo jinxed it, sorry
you clicked the little x besides the image, and then added it back?
Nope, I deleted the service and deployed it again
smh like this
not quite what i had in mind
oh could you elaborate?
click the little X to remove the image, then add it back
sweet, that worked thanks
Also, quick question
- Is it possible to deploy a service on a region that not
us-west initially?
- When 2 redis instance exists which one would the env variables point to?1. not yet
2. whatever you set it to
Curious what flow you went through to originally deploy Redis where it failed
Not sure what triggered it, I created the service twice both times it didn't deploy.
I did a region migration too, but the deploy did not happen even before that.