Reverse Proxy

The Reverse Proxy extension lets you put a secure HTTPS URL in front of any local service running on your ProxyBox or elsewhere on your network. If you have an internal web app, a device with an HTTP-only interface, or a service running on an unusual port, you can make it accessible through a clean ProxyBox URL path with TLS and CORS headers handled automatically.

How It Works

You define a path prefix and a target. When a request hits your ProxyBox at that path, it gets forwarded to the target service with the prefix stripped. For example:

A request to https://pbx-D8A4.pbxz.io/wiki/page gets forwarded to http://localhost:3000/page
A request to https://pbx-D8A4.pbxz.io/grafana/dashboard gets forwarded to http://192.168.1.50:3000/dashboard

CORS headers are added automatically, so browser-based applications can call these endpoints without cross-origin issues.

Combined with the .cloud tunnel, this gives your internal services a public, encrypted URL — accessible from anywhere without VPN or port forwarding.

Use Cases

Internal tools — Make a Grafana dashboard, wiki, or admin panel accessible through your ProxyBox URL
HTTP-only devices — Wrap an insecure device interface in TLS
Multi-service routing — Run several services on one device and give each its own URL path
Remote access to local apps — Pair with the .cloud tunnel to reach internal services from anywhere

Settings

You can create multiple Reverse Proxy instances, each mapping a different path prefix to a different service.

Setting	Type	Description
Name	`string`	A short identifier for this proxy (e.g. `wiki`, `grafana`).
Path Prefix	`string`	The URL path segment that triggers this proxy. A leading `/` is added automatically if omitted.
Target Host	`string`	The host to forward to. Defaults to `localhost` if empty. Use an IP to proxy to another machine on the network.
Target Port	`number`	Port of the target service (1 — 65535).
Start on Boot	`boolean`	Automatically start this proxy when the device boots.