Skip to main content

​
Use Tools and Reports to Check Proxy Health

The Web UI includes Reports and Support utilities that are not policy sections. Use them to confirm the proxy is healthy, audit configuration changes, and troubleshoot user issues.

​
Reports

  • Dashboard and Statistics — traffic overview and module counters (DLP blocks, scan totals, and similar).
  • Native logs, Detailed logs, Config logs — see Logging and troubleshooting.
  • Active Connections, Connection Pool — live appliance state. Useful for diagnosing a specific client’s session in real time, or when suspecting connection exhaustion under heavy load.
  • DNS Cache — live appliance state. Check here before assuming a stale DNS answer is a resolver problem outside SafeSquid. The appliance’s own cache may be the one serving it.
  • Password Cache — live appliance state. Clear it when troubleshooting a credential change that doesn’t seem to take effect. A cached failure or cached stale success can otherwise mask the real state for the remainder of the cache’s expiry window.
  • SSL Certs/Cache — live appliance state. Relevant when a client reports certificate errors that persist even after you believe the underlying HTTPS Inspection configuration is fixed.
  • LDAP Entries — directory browse after Integrate LDAP is configured. Use it to confirm a directory sync actually populated the expected users and groups before writing Access restrictions or Access Profiles rules that depend on them.
License and signature/feed status are not under Reports — that’s the separate Support top-nav page, next to Configure. See Support for its License Details panel and ten appliance-operation cards (support tarball, config backup/restore, upgrade, restart, diagnostics, live chat).

​
Other utilities

  • password — confirmed live as the xx--password mode of Support → URL Commands (the same “URL command executor” dialog used for Test the Functionalities), not a separate card. Whether individual password fields (for example HTTPS Inspection’s cached cert password) also carry their own dedicated button that opens this same tool pre-filled was not exercised — confirmed only that the mode itself exists and is reachable this way.
  • Upload templates — not a standalone tool. Each entry under Custom Settings → Templates carries its own File field (for example blocked.html). Uploading a custom block/info template is done per-entry there, via that field’s own upload control, not through a separate global “Upload templates” utility. Any policy section’s Template field (Access Profiles DENY actions, ClamAV, DNS Blacklist, and others) can then reference the uploaded template by name.
  • Subscription — activation key upload and license view (on-appliance side; distinct from the Support page’s License Details).
  • Categorize Web-Sites — local category overrides (Web UI app, not a policy section list).

​
CLI and files

  • Init script: /etc/init.d/safesquid {start|stop|restart|status|foreground|space_clean} — see Daemon.
  • Policy file: /usr/local/safesquid/security/policies/config.xml; process tunables: /opt/safesquid/startup.ini.

​
Examples

​
Confirm signature feeds after renewal

  1. Upload activation key under Subscription.
  2. Open Support — the License Details panel’s Last Updated Time should advance after the next UPDATE cycle.
  3. Reproduce a request; Detailed logs should show application_signatures when subscription is valid.

​
Recover a forgotten encrypted cache-certificate password

Open the password utility, enter the plaintext, and paste the resulting encrypted value directly into the target policy field — do not hand-construct an encrypted value or reuse one copied from a different password.

​
How to verify

  1. When troubleshooting with Reports, start with Detailed logs for a single-request question and only move to Native logs, with the matching log family enabled, once you know which module is involved.
  2. Treat Active Connections and Connection Pool as point-in-time snapshots — refresh and re-check rather than diagnosing a live capacity issue from one stale view.

​
Next steps