KevinTheJedi I created a new subdomain, fresh install, and had the same issue again. I contacted support and they said that:
hosting support
"Thank you for the provided information.
Based on my experience, this is caused by incorrect .htaccess rules. Most specifically, this one:
RewriteRule .*$ %1/http.php/$1 [L]
Should be as follows:
RewriteRule .*$ %1/http.php/ [L]
Alternatively, you should be able to authenticate successfully after you are redirected back to the website and modify the URL by adding the http.php string to after the /api, like this:
https://tickets.mysite.org/api/http.php/auth/oauth2...
and then refresh the page which would be sufficient to authenticate with OAuth2.
Note that this is not a hosting issue and you should discuss this further with the osTicket support channels should you have any questions or require further assistance in regards to this.
me
Oct 19, 2022 02:52 PM
Ok thanks. I have tried both solutions, changing the Rewrite rule to
Should be as follows:
RewriteRule .*$ %1/http.php/ [L]
throws a 500 error on the page.
hosting support
I don't see an issue as per the Apache logs as there are no new entries since you applied the change. I also tested from my end and the website's homepage opens correctly. You can try the other approach I mentioned."
On top of this, I have a separate hosting company, fresh install, new Client, etc - and same issue after Google Authentication - No input file specified.
However, on this page, I manually enter the "http.php" after api/ in the search bar and it works.
