Paths and Services

Locate the managed files, logs, and systemd units that make up a Proxyble installation.

Proxyble manages local files and systemd services on the host where it is installed. Use these locations for inspection and diagnostics; make configuration changes through the Proxyble UI or CLI so the managed components stay synchronized.

Configuration and runtime state

  • /etc/proxyble/config.ini: canonical managed configuration.
  • /etc/proxyble/allow-list/: managed Basic and Endpoint allow-list state.
  • /var/spool/proxyble/rules: pending local rule decisions.
  • /var/lib/proxyble-rule-agent: rule-agent runtime state.
  • /opt/proxyble: installed Proxyble files, including RioSQL policy templates when analytics is enabled.

Logs

  • /var/log/proxyble: timestamped Proxyble CLI and action logs.
  • /var/log/proxyble-rule-agent: daily rule-agent activity and audit events.
  • /var/log/riodb: RioDB logs when analytics is installed.

Service output is also available through the system journal:

sudo journalctl -u haproxy.service -n 50 --no-pager
sudo journalctl -u nftables.service -n 50 --no-pager
sudo journalctl -u proxyble-rule-agent.service -n 50 --no-pager
sudo journalctl -u riodb.service -n 50 --no-pager

riodb.service is present only when analytics is enabled. The Proxyble rule agent also uses proxyble-rule-agent.path and proxyble-rule-agent.timer to react to decisions and scheduled expirations.

Inspect without editing

sudo proxyble --config-view
sudo proxyble --config-status
sudo nft list table inet pmgr

The nft command shows the active Proxyble-managed firewall table. For a troubleshooting sequence and component-specific checks, continue to Review Logs and Rule Activity and Diagnose Proxyble Problems.

Removal warning

sudo proxyble --installation-remove stops services and removes Proxyble-managed configuration, logs, runtime state, and service files. Back up any audit evidence or configuration details you need before initiating removal.