Ticketix runs on a web server that your organization controls. Check these requirements before you install it.
PHP
| Requirement | Value |
|---|---|
| PHP version | 8.3 or newer; 8.3, 8.4 and 8.5 are supported |
| Database extension | PDO MySQL |
| Other extensions | mbstring, OpenSSL, cURL, ZIP, fileinfo and Sodium |
Select the PHP version for the site in your hosting control panel (for example MultiPHP Manager on cPanel). The Ticketix package does not choose a PHP version or handler for the server.
- Sodium and OpenSSL are needed for the licence check and for encrypting stored secrets.
- cURL is needed for the licence service, for updates from ARN and for AI providers.
- ZIP is needed for exports, updates from ARN, the Knowledge Base import and the release notes import.
Database
Ticketix uses a MySQL database. Create an empty database and a database user before you run setup. The database name may contain only letters, numbers and underscores. The default character set is utf8mb4.
SQLite is no longer offered for new installations from Ticketix 2.3.1. An installation that already runs on SQLite keeps working until an administrator moves its data to MySQL; see Update Ticketix.
HTTPS and web server
- Use HTTPS. The licence service is reached over verified HTTPS, and links in emails use the public address of the installation.
- Ticketix can run in the domain root or in a subfolder, for example
https://support.example.com/ticketix. - Apache: the access rules are in the included
.htaccessfile. They close thecore,scripts,langandstoragefolders and the configuration files to web access. - Nginx: add the same restrictions to the server configuration yourself: block HTTP access to the configuration files and to the
core,scripts,langandstoragefolders. Allow PHP in theapifolder as in the other application folders; the ticket API answers there.
File permissions
During installation the web server user must be able to write to the application folder (setup writes config.php) and to the storage folder. After installation, storage must stay writable. Updates from the Updates screen (from version 2.0.2) also need write access of PHP to the application folder; if you restrict it, update by hand with the update ZIP.
Ticketix uses your own mailbox:
- SMTP for outgoing mail (replies, notifications, password reset links).
- IMAP for incoming mail (recommended). A webhook or an email pipe can be used instead.
See Connect email (SMTP and IMAP).
Scheduled task
A scheduled task (cron) must run php scripts/cron.php from the application folder. It fetches and sends mail and runs SLA checks, workflows, scheduled reports, Knowledge Base publishing, the search index, AI jobs, note reminders, the weekly content gaps email, update checks and auto-closing. See Set up the scheduled task (cron).
Optional
| Feature | What you need |
|---|---|
| AI assistance and triage | An API key from OpenAI, Anthropic, Google Gemini, DeepSeek or an OpenAI-compatible server |
| Large Knowledge Base imports | PHP upload limits (upload_max_filesize and post_max_size) larger than the ZIP file |
| Two-factor authentication | An authenticator app on each staff member's phone, for example Google Authenticator or Microsoft Authenticator |
Charges for your hosting, mailbox and AI provider come from those providers and are separate from Ticketix.