Where Does osTicket Store Config and Tickets?
osTicket reads include/ost-config.php for database credentials. Tickets live in MySQL; attachments join them or a folder.
Last updated
osTicket centers on include/ost-config.php with MySQL credentials and salts, written once by the installer and rarely touched after. Tickets, users, and KB articles live in MySQL. Attachments default into the database, movable to filesystem or S3 via storage plugins with per-file backend flags.
Upgrades demand the trio: database dump, attachment files, codebase. The repair tool (repair_settings.php) fixes paths and credentials after moves but displays secrets in-browser, so delete it immediately after use. Never skip the setup/ folder removal post-install; leaving it invites reinstallation over live data.
Where osTicket stores this, by platform
include/ost-config.php (install root)
DB credentials and salts, installer-written. Guard it; it decrypts nothing but unlocks everything. Repair tool fixes paths post-move; delete it right after use.
Frequently asked questions
how do i back up osticket
Copy ost-config.php plus a MySQL dump plus the attachments folder (when using filesystem storage) with the app stopped. Tickets reference files by backend flag (D database, F files). Restore all three or links rot.
database or filesystem for osticket attachments
Install the filesystem plugin, point it at a writable folder, and migrate with manage.php file migrate. Database storage suits small loads; heavy attachment shops move to disk. The ost_file table flags each file's backend per row.
Notice an outdated path? Let us know.