Manage Proxyble Configuration

Proxyble stores its managed runtime settings in /etc/proxyble/config.ini. That file records the listener, backend, HAProxy, nftables, rule-agent, and optional RioDB settings that make up a deployment.

Use the Proxyble UI or CLI to change those settings. The commands validate related values and render the service configuration together; editing generated service files directly can leave the runtime out of sync with the saved configuration.

Inspect the current configuration

Review the managed configuration before a change, after an upgrade, or while investigating traffic problems:

sudo proxyble --config-view
sudo proxyble --config-status

--config-view shows the saved settings. --config-status adds the current service health, host information, and recent rule activity.

Configuration areas

• Listener defines the public port, traffic mode, timeout, and—when Proxyble terminates TLS—the certificate bundle.
• Backend defines the primary application destination and an optional secondary destination for round-robin balancing.
• Analytics enables RioDB and the policy workflow. It is optional and should be added only after the base listener and backend work normally.
• Enforcement state includes manual rules and allow-lists. Those are managed through their dedicated commands rather than by editing config.ini.

For a detailed choice of TCP, HTTP, and HTTPS modes, see Choose a Listener Mode. For backend addressing and failover, see Configure Backend Routing.

Use a staged change workflow

For listener or backend changes, save the settings without starting services, review the result, then start the managed runtime:

sudo proxyble --config-listener \
  --mode http \
  --port 80 \
  --timeout 60s \
  --no-start

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

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

This keeps the prior runtime in place while you review the planned listener and backend. Use a maintenance window for changes that move a public port, replace TLS material, or alter the traffic mode.

Treat TLS material as sensitive

HTTPS mode gives Proxyble the PEM bundle it needs to terminate TLS. Keep the private-key material readable only by the appropriate administrators and service account, and back it up according to your normal secret-management practice. If TLS terminates elsewhere and Proxyble should only forward encrypted connections, use TCP mode instead.

For the command groups and options used to manage a deployment, see the CLI Reference.