Getting Started
Install Proxer and expose a local HTTP service in a few minutes.
Prerequisites
Section titled “Prerequisites”- A public machine that can receive HTTP/WebSocket traffic
- A local HTTP service to expose
- Node.js 24 or later if you install from npm
Installation
Section titled “Installation”Download a standalone Windows executable from GitHub Releases.
proxer.exe --versionbrew install tinyrack-net/tap/proxernpm works on every platform and can be used as a cross-platform fallback.
npm install -g @tinyrack/proxerdocker run --rm tinyrack/proxer --versionStarting Fresh
Section titled “Starting Fresh”If this is your first time using Proxer, follow these steps to start one public server and expose one local service.
-
Start the public server
Run Proxer on the machine that receives public traffic.
proxer server --listen 0.0.0.0:8080 --domain your-server.example.com --token dev-tokenThe server listens for both public requests and tunnel control connections on the same port.
-
Start a local app
On the client machine, start any HTTP service. This example uses Python’s built-in server:
python3 -m http.server 3000 --bind 127.0.0.1 -
Connect the root-domain tunnel
Omit
--subdomainto register the root domain route.proxer http 3000 \--server ws://your-server.example.com:8080 \--token dev-token -
Test the root route
curl -H 'Host: your-server.example.com' http://your-server.example.com:8080/ -
Use a subdomain route
Start another client with
--subdomainwhen you want a named route.proxer http 3000 \--server ws://your-server.example.com:8080 \--subdomain demo \--token dev-tokencurl -H 'Host: demo.your-server.example.com' http://your-server.example.com:8080/
What’s Next?
Section titled “What’s Next?”Now that you have a tunnel running, explore the guides:
- How It Works — understand the control connection and request flow
- Routing and Trusted Proxies — configure root domains, subdomains, and reverse proxies
- Docker — run the public server from an OCI image
- proxer server — command reference for the server
- proxer http — command reference for tunnel clients