Hi guys,
I've searched through the forum but can't seem to get a resolution to my problem. Not sure if it's osTicket or hosting related.
When a new ticket is created via the 'Support Centre' and 'Create Ticket' is clicked a message pops up to say that the ticket is being created and it will take a few seconds. My issue is that it is taking 60 - 90 seconds for this to disappear and the ticket created message to appear. Sometimes it times out and doesn't show the message but still creates the ticket. However my clients don't know this and go through the process of creating the ticket again, leading to duplicate tickets.
Any thoughts?
osTicket: v1.16.6
PHP: 8.1
phpMyAdmin: 4.9.7
Database client version: libmysql - mysqlnd 7.4.30

Many thanks in advance

  • KevinTheJedi and nandi96 replied to this.

  • Update: I turned off 'Force all requests through HTTPS.' and that seems to have sorted the issue. Instead of taking 60 to 90 seconds it's taking 5 to 10 seconds.

    daleoran

    I can’t say for sure as you haven’t posted any logs but usually this can be due to the system trying to send alerts to department members, etc. and it’s taking a long time to do so. But like I said, I can’t say for sure as I cannot replicate the issue. 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.

      7 days later
      5 days later

      Hi guys,
      My apologies, I had taken some annual leave and am only getting to look at this again now.
      @KevinTheJedi - there doesn't appear to be anything in the osTicket system logs. I'll have a look at the other logs you mentioned asap
      @nandi96 - I've turned off every verification check I can find and the problem still persists 🙁

      Update: I turned off 'Force all requests through HTTPS.' and that seems to have sorted the issue. Instead of taking 60 to 90 seconds it's taking 5 to 10 seconds.

        daleoran

        Nice! Thank you for the update. You should only ever use that setting if you don’t know how to setup HTTPS redirection at the server level or you don’t have access to the server or something (like a shared host).

        Cheers.

          Write a Reply...