The OutRay CLI exposes tunnels from your local machine to the internet. Install it with: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.
Global flags
These flags are available on every command.| Flag | Alias | Description |
|---|---|---|
--version | -v | Print the installed CLI version and exit. |
--help | -h | Print usage information and exit. |
--dev | Connect to the local development server instead of production. |
outray login
Authenticate the CLI by opening a browser window to the OutRay dashboard.
outray logout
Clear the locally stored authentication credentials.
outray whoami
Show the currently authenticated user and the active organization.
outray switch
Switch the active organization. If you belong to more than one organization you can either select interactively or pass the organization slug directly.
| Argument | Type | Required | Description |
|---|---|---|---|
[org] | string | No | Slug of the organization to switch to. Omit to select interactively. |
outray <port>
Shorthand for starting an HTTP tunnel. Equivalent to outray http <port>.
| Argument | Type | Required | Description |
|---|---|---|---|
port | number | Yes | Local port to expose (1–65535). |
Request a specific subdomain for the tunnel URL. Requires authentication.
Use a custom domain instead of a generated subdomain. The domain must be configured in the OutRay dashboard first.
Run the tunnel under a specific organization for this invocation only. Does not change your active organization.
Protect the tunnel with HTTP Basic Auth. Visitors must provide this password to access the tunnel.
Override the authentication token for this invocation. Useful for CI or scripted environments.
Suppress per-request log lines in the terminal.
Also advertise the service on the local network via mDNS so devices on the same LAN can reach it at
<subdomain>.local.Start a LAN-only server with mDNS advertisement and no remote tunnel. No authentication is required.
outray http
Start an HTTP tunnel. Identical to outray <port> but makes the protocol explicit.
| Argument | Type | Required | Description |
|---|---|---|---|
port | number | Yes | Local port to expose (1–65535). |
outray <port>.
Example
outray tcp
Expose a raw TCP service to the internet. The server assigns a public port in the range 20000–30000.
| Argument | Type | Required | Description |
|---|---|---|---|
port | number | Yes | Local TCP port to proxy (1–65535). |
Request a specific public port. If the port is already in use the server assigns another.
Run the tunnel under a specific organization for this invocation only.
Override the authentication token for this invocation.
Suppress per-connection log lines.
outray udp
Expose a UDP service to the internet. The server assigns a public port in the range 30001–40000.
| Argument | Type | Required | Description |
|---|---|---|---|
port | number | Yes | Local UDP port to proxy (1–65535). |
Request a specific public UDP port. If the port is already in use the server assigns another.
Run the tunnel under a specific organization for this invocation only.
Override the authentication token for this invocation.
Suppress per-packet log lines.
outray start
Start all tunnels defined in a TOML configuration file. This is the recommended way to run multiple tunnels in development or CI.
Path to the TOML configuration file, relative to the current working directory.
Each tunnel in the config file starts concurrently. The command runs until you press
Ctrl+C, which gracefully stops all tunnels.outray validate-config
Validate a TOML configuration file without starting any tunnels. Prints a summary of every tunnel found and any validation errors.
outray validate
Flags
Path to the TOML configuration file to validate.
outray version
Print the installed CLI version.
outray -v, outray --version
outray help
Print the full usage summary.
outray -h, outray --help