TCP tunnels forward raw TCP traffic from a remote port on OutRay’s servers to a local port on your machine. Unlike HTTP tunnels, TCP tunnels work at the transport layer, so they support any protocol that runs over TCP.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/outray-tunnel/outray/llms.txt
Use this file to discover all available pages before exploring further.
Basic usage
tcp.outray.app:43210 will reach your local service on port 5432.
Flags
| Flag | Type | Description |
|---|---|---|
--remote-port <port> | number | Request a specific remote port instead of a randomly assigned one. |
--org <slug> | string | Open the tunnel under a different organization without switching your active org. |
--key <token> | string | Override the auth token. Useful for CI/CD or scripted environments. |
--no-logs | boolean | Suppress per-connection log output in the terminal. |
Connecting to a TCP tunnel
Once the tunnel is open, connect using the remote host and the assigned port number shown in the terminal output.- PostgreSQL
- MySQL
- SSH
Requesting a specific remote port
By default, OutRay assigns a random available port. Use--remote-port to request a specific one:
Example use cases
Databases
Share a local PostgreSQL, MySQL, or Redis instance with a teammate or connect a remote app to your local dev database.
SSH access
Open a TCP tunnel on port 22 to reach a machine behind a firewall over SSH.
Game servers
Expose a locally running game server so friends can connect without port forwarding.
Custom services
Any TCP-based protocol — SMTP, FTP, Redis, MQTT — works through a TCP tunnel.
Stopping the tunnel
PressCtrl+C to stop the tunnel. All open connections are closed and the remote port is released.