Command reference

tunnelize command reference can be also shown by running tunnelize help.

CommandSubcommandArgumentsDescription
initall-Initialize tunnelize.json for both tunnel and server with example configuration.
inittunnel-s, --server <SERVER>Initialize tunnelize.json for tunnel. If -s, --server is passed it will connect to tunnelize server to pull in config.
-t, --tlsUse TLS to connect to server
-c, --cert <CERT>Path to custom CA certificate file for TLS
-k, --key <KEY>Tunnel key for server authentication
initserver-Initialize tunnelize.json for server configuration
server-c, --config <CONFIG>Starts tunnelize server using tunnelize.json from current directory.
tunnel-c, --config <CONFIG>Starts tunnelize tunnel using tunnelize.json from current directory.
-v, --verboseShow detailed output for tunnel connection
monitorsystem-info-c, --config <CONFIG>Display system information.
monitorlist-endpoints-c, --config <CONFIG>List all endpoints.
monitorlist-tunnels-c, --config <CONFIG>List all tunnels.
monitorget-tunnel-c, --config <CONFIG>Get tunnel information by UUID.
monitordisconnect-tunnel-c, --config <CONFIG>Disconnect tunnel by UUID.
monitorlist-clients-c, --config <CONFIG>List all clients.
monitorget-client-c, --config <CONFIG>Get client information by UUID.
monitorlist-links-c, --config <CONFIG>List all links.
monitorget-link-c, --config <CONFIG>Get link information by UUID.
monitordisconnect-link-c, --config <CONFIG>Disconnect link by UUID.

On commands using -c, --config, if it is passed, it will load in that config json file, otherwise it will load tunnelize.json from current working directory.

Environment

Tunnelize supports setting environment variables to modify the log output. Following environment variables can be set:

NameDescriptionPossible ValuesDefault Value
LOG_LEVELSets the logging level for the applicationerror, warn, info, debuginfo
LOG_COLORSEnables or disables colored log outputtrue, falsetrue