Remote Access

ProxyBox can be accessed from anywhere on the internet — not just your local network. The difference is one small change in the URL.

Local vs. Cloud URLs

Access	Domain	Example
Local (same network)	pbx-<id>.pbxz.io	https://pbx-D8A4.pbxz.io/api/v1/status
Remote (anywhere)	pbx-<id>.pbxz.cloud	https://pbx-D8A4.pbxz.cloud/api/v1/status

The API, the request, the response — everything works exactly the same. The only thing that changes is the domain.

How It Works

When you use the .cloud domain, your request travels through an encrypted tunnel back to your ProxyBox device on your local network. No port forwarding, no VPN, and no firewall changes are needed.

1. Your application (or browser) makes a standard HTTPS request to the .cloud URL.
2. The request is routed through an encrypted tunnel to your ProxyBox.
3. ProxyBox handles it exactly as if it were a local request — printing, device access, or API calls.
4. The response travels back through the tunnel.

Use Cases

Cloud SaaS Printing

A cloud ERP or SaaS application needs to send shipping labels to a printer on your warehouse floor. Configure it to POST to your ProxyBox .cloud URL:

POST https://pbx-D8A4.pbxz.cloud/api/v1/print/tag_UPSLABELS
Content-Type: application/octet-stream
X-API-Key: YOUR_API_KEY

^XA^FO50,50^A0N,50,50^FDHello World^FS^XZ

The label prints on the local Zebra printer — even though the request originated from a server on the other side of the world.

Remote Device Management

Access the ProxyBox admin dashboard from home, a client site, or anywhere with internet access. Navigate to https://pbx-<id>.pbxz.cloud in your browser and log in as usual.

Browser LNA Bypass

Modern browsers (Chrome 142+) are rolling out Local Network Access (LNA) restrictions that block web apps from talking to devices on local IP addresses. Each web app origin triggers a permission prompt that confuses end users.

The .cloud tunnel bypasses this entirely. When your browser makes a request to a .cloud URL, it’s talking to a public address — LNA restrictions don’t apply. No permission prompts, no user confusion, no support tickets.

Enabling Remote Access

Remote access is managed through the Secure Remote Access Tunnel extension. See Extensions for configuration details.

Note

The .cloud tunnel requires an active internet connection on the ProxyBox device. If the device is offline, remote access is unavailable — but local .io access still works.

Security

• All traffic between your application and ProxyBox is encrypted end-to-end.
• The same API key authentication applies — requests must include a valid X-API-Key header (if enabled).
• No inbound ports are opened on your network. The tunnel connects outbound from the ProxyBox.