23 Replies
Project ID:
dd3f96f7-3ab3-4453-86a3-32328b2f81d6dd3f96f7-3ab3-4453-86a3-32328b2f81d6
is there a way to determine what was ?
that's a local address, likely the dashboard trying to connect
for reference, I haven't connected via any redis client
that's strange, you mean the railway dashboard?
yeah, that's my guess, but whatever it is, it's a local address so it's not an attack
idk strikes me as very strange
if it's caused by the railway dashboard, woudln't that be easy to determine?
do you have the tcp proxy enabled?
you mean, exposed to the public web?
I mean do you have the tcp proxy enabled on the redis service
(it was previously) i'ved turned it off
not sure what that is
(tcp proxy)
you definitely know what it is
(there was previously a generated domain ... which I could use to connect to it outside railway)
i turned it off now
that would be a tcp proxy
right π
If you don't have the tcp proxy enabled Railway will attempt to make a request to the open port (in this case 6379) so that we can suggest adding a domain if necessary.
mystery solved
hey, when this error happened, the tcp proxy was enabled. It was something like viaduct.proxy.rlwy.net:49184
mac, its a local address
Oh just checked and turns out we make the request regardless
ok π
Iβll raise with team though. Seeing that message in the logs is very cryptic indeed
yes, am i the first to notice it? It's a little odd looking.