Composer Dependency Issue with PHP 8.1

bawalker

I just updated osTicket for a client from 1.17.5 to 1.18.1 and also updated to PHP 8.1.31 successfully. I updated the osTicket website successfully and can navigate all pages without issue.

When I go to re-authorize email fetching from Office 365, (Remote Mailbox > Config > ldP Config > Check Outlook Scopes > Submit), I'm redirected to the 365 login page for the email account for this help desk. I proceed to login but I'm immediately given the following error:

Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0".

Can someone assist in troubleshooting?

bawalker

Here is my info from osTicket.

KevinTheJedi

bawalker

That’s strange, the helpdesk already shows PHP 8.1.31 so the requirement should be satisfied as it’s saying “greater than or equal to 8.1.0”. Did you fully update the server and site to PHP 8.1? Since the helpdesk shows PHP 8.1.31 it could be that somewhere in the site configuration it’s still set to a previous version. Make sure the handler mapping for the server and site specifically are set to the latest PHP version.

Cheers.

bawalker

@KevinTheJedi I have went through IIS removing the old PHP versions and unregistering them as I went so that only 8.0.x and 8.1.x are left. IIS shows the correct version of PHP installed, but each time I go through the email confirmation via Outlook login, I'm presented with that same page still.

KevinTheJedi

bawalker

That is truly odd and I cannot replicate...I would recommend using PHP 8.2 and retesting.

Cheers.

bawalker

KevinTheJedi I did download and install PHP 8.2.x this morning, however the same problem persists. I made sure all the handlers for old versions were removed (they are), osTicket is still giving the same error.

KevinTheJedi

bawalker

That is so odd. Check your /path/to/osticket/include/laminas-mail/composer.json file and see if you see the following:

{
...
    "require": {
        "php": "~8.1.0 || ~8.2.0",
    ...
    "config": {
        ...
        "platform": {
            "php": "8.1.99"
        }

Cheers.

bawalker

I was able to confirm that the following exists in composer.json:

"require": {
"php": "~ 8.1.0 || ~ 8.2.0",
"ext-iconv": "*",
....
},

and

"config": {
"sort-packages": true,
"allow-plugins": {
"composer/package-versions-deprecated": true,
"dealerdirect/phpcodesniffer-composer-installer": true
},
"platform": {
"php": "8.1.99"
}
},

Do I need to make changes there?

[NOTE] Added spaces between "~" and *8" to be better readable here on the forum.

KevinTheJedi

bawalker

Well then I'm stumped. Everything online suggests the server is not seeing PHP 8.1 but rather a lower version for some reason; hence why it's not satisfying the requirement and throwing the error. I'd simply recommend googling the error and trying everything people recommend. I would not recommend lowering the requirement in the composer file as that could lead to further issues in the future. You should ideally address the main issue of composer not recognizing the actual PHP version of the site.

Cheers.

bawalker

@KevinTheJedi I decided to remove and reinstall IIS after a full and complete backup earlier. I have osTicket 1.18.1 reinstalled but am getting the HTTP Error 500.19 referencing \?\C:\inetpub\wwwroot\osTicket\web.config file. I did find instructions in another forum post that instructed to make sure IIS URL Rewrite extension installed. I saw I had it installed originally, so I removed and reinstalled that.

I also noticed when I go into my Default Web Site / osTicket to click on/use PHP Manager, I do get a PHP Manager error referencing web.config as well.

Are there any specific configurations for IIS URL Rewrite that need to be made to get the web.config referenced error to go away.?

KevinTheJedi

bawalker

What specific error with the config?

Cheers.

KevinTheJedi

bawalker

All I'm seeing online is that URL Rewrite is not properly installed/enabled if you get the error about the web.config file. Here is an example:

https://forum.osticket.com/d/103734-installation-on-iis-on-windows-server-2019-not-running/6

Cheers.

bawalker

@KevinTheJedi Deleting the web.config file in both the www root and osticket folders fixed that issue. IIS now allows me to access PHP settings normally there and the osTicket site loads as it should.

When I go to admin portal > Email > Email > Email Account > Remote Mailbox > Config > IdP Config > Submit

I enter the helpdesk email address and password credentials. Instead of getting a PHP error like I did previously, now it just says Unable to connect.

I did make sure URL Rewrite Module was reinstalled as well as IIS having HTTP Redirect turned on as well. When I go through the reauthorization, I get that error in Chrome "ERR_CONNECTION_REFUSED".

So far progress is made, but I'm sure I'm missing something simple.

KevinTheJedi

bawalker

Well you need the web.config so that the URL Rewrite works.

Cheers.

bawalker

I dropped the original web.config file that I had backed up prior to making any changes in the OS ticket folder, I got the same connection refused.

So I dropped the web.config file back into the wwwroot directory from the original backup and unfortunately I still received the connection refused. I also restarted the IIS services and the server itself.

When I reinstalled osTicket, I actually restored the original wwwroot/osTicket folder that was backed up. I did decide to create a new wwwroot/osTicket-new folder in case something wasn't happy in the original folder. I copied over the ost config file and imported the authentication/oAuth plugin and now it does redirect me to the Microsoft website, however I get multi-tennant errors.

I am going to create a new App ID in Azure and try again. I'm documenting this here for others who may find this thread and need assistance for the same thing.

bawalker

I went through and created a new app registration like I have done in the past. When I log into OSTicket to re-authorize IdP, it takes me now to the Microsoft login page so I log in with the credentials. It immediately bounces back with Error 404 Not Found. (See Image below). It's referencing the path C:\inetpub\wwwroot\osTicket\api\auth\oauth2.

When I browse to that location in my newest osTicket install, that path doesn't exist. When I go inside the api folder, I just have 5 .php files like cron.php, etc. So I compared against my backed up osTicket folder to check the same path. It also does not have the auth folder and has the same 5 php files.

This leads me to believe the callback endpoint is incorrect (it's currently: http://localhost/osTicket/api/auth/oauth2), but I'm not sure what it should be so I can update it in the app registration as well.

I appreciate the very helpful assistance!

KevinTheJedi

bawalker

The path isn't real, that's why you need URL Rewriting + the web.config file. The web.config file tells the webserver how to forward the paths including the API routes. So, /api/auth/oauth2 will be redirected to api/http.php which will forward the call to the relevant backend functions. With this in mind, this error means you do not have url rewriting installed/enabled or the web.config file is missing or it's not being picked up by your server.

Cheers.

bawalker

Turns out I forgot to replace the web.config in the wwwroot/osticket folder. Once I did that I started receiving the cURL 60 error of which I found your post with another user from sometime ago. I downloaded the correct PHP certificate and edited the php.ini and everything then re-authorized with 365.