proxer http
Expose a local HTTP service through a tunnel.
proxer http <port> connects a client-initiated tunnel to a public Proxer server and forwards requests to a local HTTP port.
proxer http 3000 --server ws://your-server.example.com:8080 --subdomain demo --token dev-tokenOptions
Section titled “Options”<port>— local HTTP port to forward to. This positional argument has no environment variable.--server <url>— public Proxer server URL. Proxer always connects to/__proxer__/controlinternally.--subdomain <name>— register a subdomain route. Omit it to register the root domain route.--token <token>— shared token matching the server.
Environment Variables
Section titled “Environment Variables”PROXER_SERVER— default value for--serverPROXER_SUBDOMAIN— default value for--subdomainPROXER_TOKEN— default value for--token
CLI flags take precedence over environment variables.
Root Route
Section titled “Root Route”Omit --subdomain:
proxer http 3000 --server ws://proxy.example.com:8080 --token dev-tokenRequests for proxy.example.com are sent to the local service.
Subdomain Route
Section titled “Subdomain Route”Pass --subdomain:
proxer http 3000 --server ws://proxy.example.com:8080 --subdomain demo --token dev-tokenRequests for demo.proxy.example.com are sent to the local service.
Reconnect Behavior
Section titled “Reconnect Behavior”If an established control connection drops, the client retries and registers again when the server is reachable. If the initial connection fails before the client is registered, the command may exit.