Upgrading from from 1.14 to 1.17

PSC-IT

Hello Team,
I am unable to work out why OS ticket will not let me upgrade to 1.17. I have unable to get anything going from 1.14 to 1.17, but when i go from 1.14 to 1.16 i get somewhere.
I have followed the procedure, but I seem to get stuck at changing the PHP version on the IIS 8 server here.
When i swap it to PHP version 7.3.7 to 8.1.1 i get the Internal server 500 error, when i swap it back to 7.3.7 i get the below window

Please help, thank you! 🙂
My SQL V5.5
OS ticket 1.14
PHP version 8.1.11
Windows 2k12 IIS 8

pcjkollmorgen

I would likely stick with PHP 8.0.x but 8.1 should be fine for 1.17 too.

In order to avoid the internal server 500 error you may want to disable all your plugins before the upgrade as there is a good chance it is a plugin which is causing the error. Certainly you will need the latest versions of the plugins obtained from the OsTicket.com / download website too, these are the most up to date and need to be updated along with the source code when changing to 1.17.

It is usually possible to find the cause of the internal server 500 errors as they usually shows up in either your web server or PHP logs.

Your screenshot is showing when you have PHP 7.3.6 installed, OsTicket 1.17 will never work with version of PHP.

PSC-IT

Thanks for the reply pcjkollmorgen !
Ok ill give that a try
If I select any PHP 8.x.x i cant even get to the upgrade screen, this is the only way i can get anything by unselecting PHP 8.x.x and selecting 7.3.6. I know it wont work, but its the only way i can get anything to show! 🙁

PSC-IT

Just reading that IIS Version 8 doesn't support PHP version 8.x.x ? Can anyone confirm that ? That is possibly why!

ntozier

Correct. Microsoft ended support for PHP 8+ back in 2020.
That does not mean that you cannot get it to work... but I will say that after running osTicket under IIS for about ten years now, I have left Windows with IIS in favor of Linux with Apache for osTicket 1.17.

PSC-IT

Thanks @ntozier, do you have any tips to get it to work ? I will eventually move to Linux, but in the short term we just need the helpdesk system back up and running 🙂

PSC-IT

Hi team,
I have managed to upgrade and get it working whilst we move to Apache, shoot me a message if you need any help 🙂

PSC-IT

Hi Team,
Managed to get it working, but the oAuth stuff still wont pick up mail 🙁
I seem to be getting this error :
cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://login.microsoftonline.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx/oauth2/v2.0/token

We were running a http version of OS ticket, so I have created a self signed domain certificate to enable SSL as Azure wouldnt accept http, could this be the problem?

I have also added the cacert.pem to the php.info file as many people have stated but still cant get working. Please help i am going a little bit batty getting this going!!!!

geseronta

PSC-IT

Did you download the cert to the local server and point the php.ini at that file? Does the file folder it resides in have proper permissions? Windows box here, I just created a new folder c:\CurlCACert\ and put the pem in there, then in php.ini pointed it at that file.

leonlongoria

I had a similar issue with our organization. The issue was our organization was using a sort of URL filter/firewall that was messing with the way SSL certs put on websites or something. We had to add a specific cert into the cacert.pem file. We just added it to the top of all the other ones and then it worked for us.