Hi,

This is my first post. I have installed the latest osTicket. My details are as follows.

Server Information
osTicket Version v1.15.8 (0daca43) — Up to date
Web Server Software Microsoft-IIS/10.0
MySQL Version 8.0.33
PHP Version 7.4.3

When I create a new ticket or close a ticket, I am faced with this error.

Inspect Element show this.
/support/scp/tickets.php?id=45#reply:1
POST https://mydomain.here/support/scp/tickets.php?id=45 500

Please update, im in a fix.

Jeet

  • KevinTheJedi replied to this.
  • bp6948

    Then you definitely need to check your logs (general server logs, webserver error logs, PHP error logs, MySQL/MariaDB error logs, osTicket System Logs, Browser Console logs, etc.) for any related errors.

    Cheers.

    jeets911

    1. You are using an old, unsupported version of osTicket. You need to upgrade and retest.
    2. You need to check your logs (general server logs, webserver error logs, PHP error logs, MySQL/MariaDB error logs, osTicket System Logs, Browser Console logs, etc.) for any related errors.

    Cheers.

      KevinTheJedi
      You are using an old, unsupported version of osTicket. You need to upgrade and retest.
      How do i do that, i also realized that i am on old, isnt there a way to update?

        Not trying to thread steal, but I am having the same issue. I was on 1.17,x upgraded to 1.17.4, and then upgraded to 1.18.

        Anytime we would try to login on the public side, post a reply, or update settings we would get a 500 error. We have reviewed logs and aren't seeing anything that would lead us directly to an issue.

        After the upgrade to 1.18, we are unable to remove oath plugin. Oauth2 Client (1) (defunct — missing). If we click delete it gives 500 error. We deleted all emails and setup a new temporary email just to be sure. Still seeing the same issue.

          bp6948

          Then you definitely need to check your logs (general server logs, webserver error logs, PHP error logs, MySQL/MariaDB error logs, osTicket System Logs, Browser Console logs, etc.) for any related errors.

          Cheers.

          Write a Reply...