The dreaded HTTP 500

Snacob

Hey friends,

first time poster here and I have limited experience with osTicket as a whole. Recently, I've decided to spin up an osTicket 1.18.x EC2 instance on AWS as a small-medium size company ticketing system.
Installation when great, was able to connect to the instance and configure it. I let my coworker install the oauth2 plugin and through a little trial and error, we were able to get it to show in our plugins list. He configured oauth2 and immediately lost connectivity to the instance. I have only been able to access the instance with putty since.
I've been checking logs but they don't exactly make sense to me. Hoping to find some help here.
Log included:

KevinTheJedi

Snacob

Do you have another application on the same server that uses Guzzle_HTTP library? Seems like a conflict of libraries where another instance of Guzzle is being loaded before the one for osTicket and the other one is older and missing a required method. Maybe you also have another plugin installed? If so, which one(s)?

Cheers.

Snacob

Not that I am aware of. It was a baseline Ubuntu 22.04 installation, threw osTicket 1.18 on it, fiddled around with Oauth2 plugin, then lost it. Checking now to see if I can find anything that would be using Guzzle.

Thank you for the reply!

KevinTheJedi

Snacob

Where did you download the OAuth2 plugin from? If from our official website, did you select 1.18.x in the "osTicket Version" dropdown on plugin selection screen?

Cheers.