Ticketix runs on your own server, so a few tools help you keep it healthy. All of them are for administrators.
Where to find it: Setup → System → Tools; in the menu, Setup → Tools and updates. The same section of the setup sub-menu holds Updates, Export and License.
The Tools screen
The top of the screen links to the health check (System health). The panels:
| Panel | What it shows or does |
|---|---|
| Overview | Queued mail, search index size, searches without results, the PHP version, database driver, IMAP and OpenSSL extensions, upload_max_filesize, post_max_size, memory_limit and max_execution_time |
| Queued, sent and failed mail, whether SMTP and IMAP are enabled, and a link to the Mail center | |
| Search | Index records, Queue pending and suggestions; Rebuild the search index rebuilds the index of Knowledge Base, community and ticket content, Process the search queue processes waiting index jobs |
| Storage | Total storage, Mail JSON files and Log files, each storage folder with its path, status, size and whether it is writable, and the maintenance actions |
| Logs | The latest lines of each log, for example system, mail, search, automation and cron, with the size and time of each log file |
| Inspector | A short summary of how the installation works, for example the ticket scope of administrators and agents |
| System checks | Database check, Mail check, Storage check, API check and Queue check, each with Run; they do not change any data |
Storage maintenance
On the Storage panel, each action has its own Run button and asks for confirmation:
- Full maintenance runs the orphan file clean-up, the old mail JSON clean-up and the old log clean-up together.
- Orphan file cleanup removes attachment files that no ticket uses.
- Mail JSON cleanup removes mail payload files older than 30 days.
On the Logs panel, Clean old logs deletes log files older than 7 days.
These actions remove working files only; tickets and their messages stay in the database.
Delete a ticket completely
Delete a ticket completely, below the panels, permanently deletes a ticket with its messages, attachments and mail records. Choose the ticket, click Delete a ticket completely and confirm. This cannot be undone. Agents close tickets instead.
Health check for monitoring
health.php reports whether Ticketix is installed, whether the storage, attachments and logs folders are writable, whether the database answers and whether the schema is in place. It answers with JSON and HTTP status 200 when everything is fine, or 503 when a check fails.
- A signed-in administrator can open it with System health on the Tools screen.
- A monitoring service sends the
health_secretfromconfig.phpin theX-Health-Secretheader, for example tohttps://support.example.com/health.php.
Without a valid secret or an administrator session, health.php answers "Not found".
Security check on the server
Run this command from the application folder to check the basic security settings:
php scripts/security-preflight.php
It checks that debug mode is off, that the secrets in config.php are strong, that config.php and .htaccess exist and that the storage folder is protected. The result is JSON with "ok": true when all checks pass.
Back up Ticketix
Back up these items regularly and before every update, to a place with restricted access:
| Item | Why |
|---|---|
| The database | Tickets, customers, articles and settings (for SQLite, the database file is in the storage folder) |
config.php | Database details and the secrets of the installation |
The storage folder | Attachments, Knowledge Base images, logs, licence files and ai-secret.key |
storage/ai-secret.key encrypts the stored AI provider keys and the authenticator secrets. Without it, AI keys must be entered again and two-factor authentication must be reset.
For a portable copy of your data, administrators can also download the Full package under Setup → System → Export. See Reporting, recurring problems and exports.
To restore, put back the application files, config.php, the storage folder and the database together.