Hello all,

I'm new to osTicket and i would like to upgrade our old osTicket version to the latest one. The main reason is because our vulnerability scanner found issues in our old version.

I've been reading the documentation how to upgrade but as i want to upgrade from an old version i'm not sure if that is the way to go ?

Current version:
v1.9.12 (19292ad)
Apache/2.2.15 (CentOS)
MySQL 5.1.73
PHP 5.3.3

As the CentOS version, MySQL and PHP version is also outdated i prefer to build a CentOS based setup from scratch. Also the current PHP version 5.3.3 is not compatible with the latest osTicket version which requires version 7.

I know how to install CentOS, Apache with PHP and MySQL. But what about osTicket without loosing any data/settings? Can i restore a 1.9.12 osTicket database on the latest version for example?

If not, what would be the best upgrade steps?

This guide is from to a different version, but the basics still apply.
https://tmib.net/upgrading-osticket-1-10-x-to-current-1-11-0/

BAck up your database.
Setup the new server.
restore the back up to the new server.
install the osTicket archive files to where you want them on your new server.
copy your /install/ost-config.php from tjhe old server to the new one.
Edit it for the new database name, username, and password.
Browse to the new site. The upgrader will upgrade the database to the format for the new version that you installed.

Latest osTicket requires 5.6, it runs better under 7.x.

8 days later

Thank you
Everything works fine, until i rebooted the server after installation.

This site can’t provide a secure connection
<URL> sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Did your old server have an SSL cert?
Does the new one?

Yes it has a SSL cert. And the new one too.
If i restart httpd a few minutes after the server has been rebooted all works fine.

Sounds to me like something isn't loading right on server boot. Hmm.

I think that this one is beyond my experience with Apache. I'll ask the devs if they have any suggestions.

@Joriz

If you reboot the server and Apache is not working correctly but then you restart Apache and everything is fine then that means the initial server startup has something wrong/misconfigured. When you restart Apache, it kills the Apache process completely and restarts it using the configurations in the config files (what startup is supposed to do but like I said you might have something misconfigured on startup). I assume that when you rebooted the server something was misconfigured causing Apache to not be fully configured or something and when you restarted Apache itself, it picked up the correct configurations, etc.

Now, I'm just completely guessing at this point as it's damn near impossible to pinpoint the cause of an issue like this without logs, etc.

Cheers.

Write a Reply...