Officially it's anything listed at https://osticket.com/faq/ which is PHP 5.6 or above and MySQL 5.0 or above (bear in mind PHP support for osTicket 1.11 stops at 7.2), although as a security minded person myself I'd advise going for 7.2 and the latest MySQL version. Old versions are a security nightmare!!
Couple notes, Peter (project lead) said something about PHP 7.3 being supported soon [my guess is next release].
I had some issues when I tried installing MySQL8 with PHP older than 7.1.16. You should not have the same problem with PHP 7.1.16+ or PHP 7.2.4+.
And while the FAQ doesn't mention it MariaDB is a viable alternative if you wish you get away from Oracle MySQL. But it isn't "official" per se.
ntozier Indeed, I've been using MariaDB ever since I started using osTicket (with an unsupported PHP 7.2 *cough* *cough*). It's standard on all Fedora builds, and uses exactly the same commands as 'real' MySQL, so shouldn't have any compatibility issues.
For what it's worth, I'd recommend MariaDB too, but that's primarily because I hate Oracle ?
ntozier I'm afraid I can't really do a proper comparison, as I've been using MariaDB as default for years in pretty much all Linux servers, and my osTicket DB is still on the small side (only started at 1.10.4). I've never once had any reason to switch to Oracle's offering though, so while I can't attest to speed, I can to compatibility!
Understood. Thanks for the compat testament. ?
Can we get an update on mysql8 compatibility? I need to migrate from 5.5 to a new corp v8 mysql and this is not a viable option for us.
I wrote an article about it a while back:
https://tmib.net/installing-osticket-1-10-4-troubleshooting-mysql8-and-php-older-than-7-1-16/
Short version I got osTicket 1.10.4 running under MySQL 8 some time ago. I was of the opinion that it was only a problem on older versions of PHP.
As a side note make sure that you specify the db is utf8 when you create it,
@ntozier blogpost is a really good read on this subject. Basically, osTicket is fine with MySQL 8 (and MariaDB’s equivalent) as long as you set the default character set to utf8 (or specify utf8 when creating the db) and making sure that the default password method is native or ensure the database user has native method.
Cheers.
KevinTheJedi @ntozier yes, I read all of the specifics around setting the default character set on the instance to utf8 and enable native (legacy) password support. The issue is that this runs on a corporate mysql server and they are unwilling to make this instance change for the character set just for a one-off like mine. their take is that you should be able to tell the app to use utf8mb4. There is also support for this in PHP 8. Furthermore when you set this setting on a mysql instance you get this message indicating it's best practice to use utf8mb4: [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. So the real question is when will OSTicket be PHP 8 and MySql 8 (with utf8mb4 support) compatible?
MySql 8 (with utf8mb4 support) compatible
We already support MySQL 8.0....we will support utf8mb4 with v2.0 as too much depends on utf8 currently.
As for PHP 8.0 support, we will start working on the support after it has been officially released.
Cheers.
At the current rate of release going on at php.net I would guesstimate that they will release PHP8 in like 2022. I think that we might see 7.4.0 by xmas though.
note: I stand corrected. PHP 8 is expected to be released in September 2021. Also 7.4.0 expected Nov 28th, 2019.
@ntozier KevinTheJedi If you get the utf8mb4 support done I don't care about PHP 8. 
Thanks for the support guys.
