We experience error when uploading file on osticket/upload/tickets.php site by user.
Error says: File Upload Error: #filename# udefined500.
Previously on 1.15 we did not experience the issue, however we updated to 1.16 recently.
Can someone please help us how to troubleshoot or solve further?

Many thanks!

Config used:
osTicket Version v1.16.3 (e148727) — Up to date
Web Server Software Apache/2.4.53 (Win64) OpenSSL/1.1.1n PHP/8.0.19
MySQL Version 10.1.36
PHP Version 8.0.19

    adamfekete

    Inspect the page, go to the network tab, make the request, and look at the Response for the request in the Network tab.

    Cheers.

      Hi KevinTheJedi
      Request URL: https://absddfsdk.com:4443/osticket/upload/ajax.php/form/upload/ticket/attach
      Request Method: POST
      Status Code: 500 Internal Server Error
      Remote Address: 1xxxxx.192:4443
      Referrer Policy: strict-origin-when-cross-origin
      Cache-Control: no-store, no-cache, must-revalidate
      Connection: Close
      Content-Length: 17
      Content-Type: text/html; charset=UTF-8
      Date: Wed, 28 Sep 2022 14:27:35 GMT
      Expires: Thu, 19 Nov 1981 08:52:00 GMT
      Pragma: no-cache
      Server: Apache/2.4.53 (Win64) OpenSSL/1.1.1n PHP/8.0.19
      Status: 500 Internal Server Error
      X-Powered-By: PHP/8.0.19
      Accept: /
      Accept-Encoding: gzip, deflate, br
      Accept-Language: en-US,en;q=0.9,hu;q=0.8
      Connection: keep-alive
      Content-Length: 1755335
      content-type: multipart/form-data; boundary=------multipartformboundary1664375257640
      Cookie: OSTSESSID=jm63lgjvu27frqh8hdhdakg284; s_fid=188C73577AE090B5-2D5EB19824C028D1
      Host: absddfsdk.com:4443
      Origin: https:// absddfsdk.:4443
      Referer: https:// absddfsdk.:4443/osticket/upload/tickets.php?id=20773
      sec-ch-ua: "Google Chrome";v="105", "Not)A;Brand";v="8", "Chromium";v="105"
      sec-ch-ua-mobile: ?0
      sec-ch-ua-platform: "Windows"
      Sec-Fetch-Dest: empty
      Sec-Fetch-Mode: cors
      Sec-Fetch-Site: same-origin
      User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36
      X-Requested-With: XMLHttpRequest

        KevinTheJedi
        Response: File is too large
        It is very interesting as we did not had this issue before. I am testing with a 1.7MB file while the settings is 32MB file limit for Attachment on Tickets and also on Attachments Storage and Settings.
        Any idea what could be the cause or how to resolve it?
        Thank you

          adamfekete

          There are older threads that explains the changes needed in Apache and potentially PHP-fpm if you’re running it.

          Cheers.

          Hi @KevinTheJedi
          Is there any chance you could be a bit more specific? I tried to read the related topics, but could not find anything that might work or we have not yet tried.
          Thanks,
          Adam

            adamfekete

            You can Google this to find the answers but:

            • upload_max_filesize
            • memory_limit
            • post_max_size

            Cheers.

            Hi @KevinTheJedi We tried all, but seems to be something else..
            We traced it further and in filedrop.field.js?e148727 we can see that this part returns the server response improperly.

            We could not find any reason why this is not working or how to resolve. Any chance that you could help us?

            Thanks
            Adam

            8 days later

            Did you check the settings in PHP that Kevin mentioned?

            upload_max_filesize
            memory_limit
            post_max_size

            Did you increase the sizes of those attributes, and then restart the webserver service?

              Hi ntozier ,
              Thank you for reaching out to us. Unfortunately issue remained the same. We did the checks & changes suggested by Kevin, but nothing has changed.
              Also, we upgraded last Thursday to 1.17, but no change on this error.
              Do you have any idea or suggestion how to troubleshoot further?

              Many thanks,
              Adam

                Write a Reply...