Fresh Install, having odd issues

OldBill

So, this has been quite an adventure for me. Trying to determine what I was doing wrong. A short history of the last 2 weeks. Have Synology NAS, was trying to use Docker to host a 1.17 version of osTicket. I was doing very well, and even had the entire OAuth2 setup with my works Azure/entra app system and could login as agent, and staff could login as users. So it was testing well. That is until I noticed TNEF was built into internal emails, so anyone messaging the ticket system directly to create a ticket, the IMAP would fail to understand TNEF...and well things would start failing and I would get 30 error alert emails every 2mins the email failed to load into osTicket. Frustrated, I scrapped that setup, and moved to Synology directly hosting, PHP8.2, and the latest 1.18 of osTicket. Downloaded it, installed, build a new db in Mariadb. It installed cleanly and beautifully. Until i got to OAuth2 setup...this is where things got different. No matter what I did, the return redirect the plugin wanted to use is /api/oauth instead of /scp/oauth - even when I tried to set the address to scp in the plugin, it said it had to be api. This would then fail to redirect correctly from microsoft. I could login, but then coming back to osTicket would hit a failed to load page. AI of course told me it was because osTicket should be expecting scp instead of api, and api is specifically for email IMAP. I then noticed that some things in 1.18 weren't looking right. All the tooltips (?) i hover over are lacking any information. As well, any of the popups for setting passwords for agents are empty too.

So, out of abundance of caution, I deleted the entire thing, and reinstalled fresh all over again. Redownloaded the 1.18 intall package, didn't get any plugins yet. I'm in...but I have the same issues with the tooltips and setting passwords. So I'm now thinking there is something fundamentally wrong with my setup, and it could have been the real issue for my Oauth not working.

Any insight would be greatly appreciated. Have I missed something?

KevinTheJedi

OldBill

Never listen to AI. It is nowhere near close to actually understanding issues. Your problem is NGINX; it is not fully supported out of the box. The software prerequisites state Apache and IIS is supported. With NGINX you have to go online to find a full working osTicket site config and manually update your NGINX configurations. It’s not like Apache, LiteSpeed, and IIS where you can use .htaccess files and web.config files respectively to do rewrites, etc.

Cheers.

OldBill

Thank you KevinTheJedi, that was the trick I was missing. Swapped it to Apache and now all that works!

I try not to use AI for this stuff, but it's hard to escape now that nearly every company is putting AI in everything. I have been lurking on here reading all your answers and learning a lot on how to use osTicket. I appreciate your expert help! Have a great Friday!