Manage the Proxyble Runtime

After the listener and backend are configured, Proxyble manages the services that receive traffic and apply enforcement. Run management commands with root privileges.

Start and restart

Start the runtime stack after configuration changes:

sudo proxyble --yes --config-start

--config-restart is an alias for the same operation. Proxyble applies the rendered configuration by stopping and starting the necessary services.

Depending on the selected mode, the runtime includes:

• nftables.service for packet-filtering controls.
• haproxy.service for the listener and backend routing.
• riodb.service when analytics is enabled.
• proxyble-rule-agent.path and proxyble-rule-agent.timer to process rule decisions and expirations.

Check status

Use the status command to review service health, host resources, and recent rule activity:

sudo proxyble --config-status

To view the managed configuration, including listener, backend, and service settings:

sudo proxyble --config-view

The canonical configuration file is /etc/proxyble/config.ini. Prefer the Proxyble UI or CLI for changes so related service configuration stays synchronized.

Stop carefully

Stop the runtime stack with:

sudo proxyble --yes --config-stop

Stopping pauses traffic protection; it does not uninstall Proxyble or erase saved rule-agent state. Use it only during a planned maintenance or rollback window, and confirm how clients will reach the protected service while the listener is stopped.

For service output and rule audit trails, continue to Logs and Audit.