Skip to main content

​
Prerequisites

​
Enable external access

By default, Railway databases are only accessible from within your Railway project’s private network. To connect from VexiData, you must enable public networking.
1

Enable TCP Proxy

  1. Log in to your Railway Dashboard
  2. Select your project
  3. Click on your database service (PostgreSQL or MySQL)
  4. Go to the Settings tab
  5. Under Networking, click Enable TCP Proxy
  6. Railway will assign a public domain and port
2

Get your connection details

After enabling the TCP Proxy:
  1. Go to the Connect tab on your database service
  2. Copy the public connection parameters (not the private/internal ones):
ParameterExample
Hostroundhouse.proxy.rlwy.net
Port43721 (randomly assigned)
Databaserailway
Usernamepostgres (PostgreSQL) or root (MySQL)
PasswordYour database password
Railway assigns a random port for the TCP proxy — it won’t be the standard 5432 or 3306. Make sure you copy the public port, not the internal one.
3

Add the connection in VexiData

  1. Go to Data Sources in VexiData
  2. Click PostgreSQL or MySQL depending on your database type
  3. Fill in the details:
For PostgreSQL:
FieldValue
Display NameA name to identify this connection (e.g., “Railway Production”)
HostYour public proxy host (e.g., roundhouse.proxy.rlwy.net)
PortYour assigned proxy port (e.g., 43721)
Databaserailway (or your database name)
Schemapublic (default — change if your tables are in a different schema)
Usernamepostgres
PasswordYour database password
For MySQL:
FieldValue
Display NameA name to identify this connection (e.g., “Railway Production”)
HostYour public proxy host (e.g., roundhouse.proxy.rlwy.net)
PortYour assigned proxy port (e.g., 43721)
Databaserailway (or your database name)
Usernameroot
PasswordYour database password
4

Test and save

Click Test & Save Connection. VexiData will verify it can reach your database. Once connected, your schema will be analyzed automatically.

​
Troubleshooting

  • Make sure you’ve enabled TCP Proxy in your database service settings. Without it, the database is only accessible from within Railway’s private network
  • Verify you’re using the public host and port from the Connect tab, not the private/internal ones. Internal URLs ending in .railway.internal won’t work from outside Railway
  • Check that your Railway project is active and the database service is running
  • Railway uses a randomly assigned port for the TCP proxy, not the standard 5432 (PostgreSQL) or 3306 (MySQL). Copy the exact port shown in the Connect tab under the public connection details
  • Double-check your username and password from the Railway Connect tab
  • PostgreSQL defaults to postgres as the username, MySQL defaults to root
  • You can view or reset credentials in the database service’s Variables tab
  • Confirm your tables are in the public schema (PostgreSQL). If they’re in a custom schema, update the Schema field in VexiData
  • Check that you’re connecting to the correct database name