Configure Backend Routing

Route allowed Proxyble traffic to one local or remote backend, or distribute it across two backends.

The backend is the application, API, or service that receives traffic after Proxyble allows it. Configure the listener and backend as separate steps so you can review the complete route before starting services.

One backend

For an application running locally on port 8080, point Proxyble at loopback:

sudo proxyble --config-backend \
  --primary-host 127.0.0.1 \
  --primary-port 8080 \
  --no-secondary \
  --no-start

Use a remote IP address or DNS name when the protected application runs on another host. Do not use the same loopback port for both the Proxyble listener and the backend, or traffic would be routed back to the listener.

Two backends

Proxyble can configure a primary and secondary backend. When both are present, HAProxy distributes traffic between them with round-robin load balancing.

sudo proxyble --config-backend \
  --primary-host 10.0.0.10 \
  --primary-port 8080 \
  --secondary-host 10.0.0.11 \
  --secondary-port 8080 \
  --no-start

This is useful for a small redundant service pair. It does not replace broader service discovery, health-check, or load-balancing design for a large fleet.

Apply and verify

After both listener and backend settings are complete, start Proxyble:

sudo proxyble --yes --config-start
sudo proxyble --config-status

Make a normal request to the listener and confirm that it reaches the expected backend. If it does not, check the configured values with sudo proxyble --config-view and then follow Diagnostics.