I have a PostgreSQL database on Railway with public TCP proxy disabled for security reasons. I'm trying to connect to it locally from my Windows machine using the Railway CLI without exposing the database publicly.

When I run:

railway connect Postgres --tunnel-only

I get the error:

Connection URL should point to the Railway TCP proxy

According to the Railway documentation (https://docs.railway.com/cli/connect), the --tunnel-only flag should create a local SSH tunnel without requiring a public TCP proxy. However, this flag doesn't seem to be working on my version of the Railway CLI.

My setup:

• OS: Windows 11
• Railway CLI version: v5.57.12+ (latest)
• Database: PostgreSQL (private, no public TCP proxy)

What I've tried:

• railway connect Postgres → requires public TCP proxy

• railway connect Postgres --tunnel-only → "Connection URL should point to the Railway TCP proxy"

• Updated to latest CLI version

What I need:

A way to create a local tunnel to my private database using the Railway CLI without enabling public TCP proxy, ideally for use with DBeaver or other database clients.

Is there an alternative command or solution available?