FLEET OVERWATCH User manualVersion 4.9.2

Server administration: issues, IP access, CPU, alerts, landing page and registrations

Version 4.9.2Updated 2026-11-02Who: Server administrator

Who: server administrators (the server's own admin sign-ins; companies do not see these pages).

Issues #

Admin › Issues (and the card at the top of the Command center) lists everything wrong on the server: failing or warning health checks, problems the automatic checks are fixing, new and reopened program errors, and automatic IP blocks. Open an issue for its severity, component, first and last seen, how many times, diagnostics, automatic fixes, stack trace and history.

  • Acknowledge (you are on it), Add note, Resolve (with a note), Reopen.
  • Run the fix now runs the recovery action for that check; Resume automatic fixes when they were held after too many tries.
  • Health problems resolve by themselves when they recover; errors and security issues are resolved by a person.

IP access #

Admin › IP access blocks addresses or ranges (203.0.113.7, 203.0.113.0/24, 2001:db8::/32) from every page and the API, and trusts the ones that must never be blocked.

  • Add an address: block or trust, for how long, and why. change and unblock / remove in the lists.
  • Automatic blocking (each limit can be changed; 0 turns it off): failed sign-ins (10 in 15 minutes), refused requests from someone not signed in (60 in 5 minutes), requests for well-known attack paths (5 in 10 minutes). Blocked for 1 hour, then 24 hours, then 7 days, then until removed.
  • Busiest suspicious addresses and Security events; select an address for its whole history.
  • You cannot block your own address. The server itself is never blocked automatically. Locked out: sudo -u www-data php /opt/fleet-overwatch/worker.php ip-unblock ADDRESS (or all).
  • Behind a proxy or load balancer, list it under Your proxies so visitors' real addresses are used.

What uses the CPU #

Admin › What uses the CPU shows the busiest processes now (what each is: a worker part, the web server, the database) and, for the last 15 minutes, hour or day, the program operations and companies that used the most CPU time, with calls, average and slowest times, memory and errors.

Admin alerts #

Admin › Admin alerts chooses, per kind of event (security, health and automatic fixes, program errors, updates, registrations, backups), whether you are told in the program and by email, and from which severity. Extra addresses can be added. Emails go through the site email server. The same alert is sent at most once in 30 minutes.

Landing page #

Admin › Landing page edits every text of the public page (headline, introduction, buttons, features, preview, platform, benefits, contact), adds a notice at the top, and shows or hides parts (demo and sign-up buttons, sections, the contact form). Plain text only; an emptied box goes back to the standard text; Back to the standard page undoes everything.

Company registrations #

Admin › Company registrations: how new company accounts open.

  • By invitation (standard): a prospective company sends a request; you are told (with every detail); Approve emails an invitation code (shown once to you too); they enter it with that email at signup.php and create the account; you are told when it exists. Reject (optionally telling them why), New code (replaces the old one), Revoke. Codes expire (7 days by default) and work once. Every step is in the request's history.
  • Open sign-up (as before) or Closed.

Prepared by Franko.

Something here out of date or unclear? Tell your administrator and mention “server-admin-44” and version 4.9.2.