<machine>.boxd.sh, or at <machine>.nyc.boxd.sh for a machine in New York. The boxd proxy terminates TLS and forwards HTTP requests to your machine.
Get started
nginx is pre-installed and configured on port 8000, but disabled by default. Start it:https://myapp.boxd.sh to see a welcome page.
Run your own app
The default proxy detects the port your app listens on among 80, 443, 8080, 8000, 3000, 5000 and 5173, and falls back to 8000. A process listening on one of those ports is reachable over HTTPS with no configuration.Change the port
To send the default proxy to a specific port, set it from your laptop:--vm to target the machine you are in:
Subdomain proxies
Create additional subdomains pointing to different ports:WebSockets
WebSocket connections work transparently. The proxy detects theUpgrade: websocket header and forwards the connection.
Non-HTTP traffic
The HTTPS proxy speaks HTTP only: it terminates TLS and routes by domain. To reach a database, an SSH daemon, a game server, or any other raw protocol, add a raw port forward instead:HTTP to HTTPS
Plain HTTP requests tohttp://<machine>.boxd.sh are redirected to HTTPS automatically. HSTS headers are included in the response.
DNS
A DNS record is created automatically when your machine boots. The record has a 60-second TTL.Custom domains
You can use your own domain instead of<machine>.boxd.sh: one domain for one machine, or a wildcard delegated to your whole organization. See Custom domains.