You are auto migrating our redis to metal when it does not work for us and I have already clicked something is wrong before.

We have a micro service architecture in which both Remix js and Nest js connect to same redis and communicate with each other. This is broken when we upgrade to metal.

We tried migrating our service instances too but that does not work either. It works when we use public url for redis

Can you guys help us migrate to metal? Currently we cannot as Redis does not work.

I raised an issue before but looks like railway crashed our project again. I think the team needs to look at this.

Previous thread: https://station.railway.com/questions/redis-not-connecting-on-railway-metal-afa3872e

Error in Nest:

```

default: connect ETIMEDOUT [ioredis] Unhandled error event: Error: connect ETIMEDOUT at Socket. (/app/node_modules/.pnpm/ioredis@5.4.2/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:633:28) at Socket.emit (node:events:519:28) at Socket.emit (node:domain:488:12) at Socket._onTimeout (node:net:595:8) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7)

```

Error in Remix:

```

[ioredis] Unhandled error event: Error: connect ETIMEDOUT at Socket. (/app/node_modules/.pnpm/ioredis@5.4.2/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:609:8) at listOnTimeout (node:internal/timers:588:17) at processTimers (node:internal/timers:523:7)

```