This is a brand new installation and everything (so far) is working perfectly, except we can attach any attachments. This happens on the customer and staff side.

This happens on all browsers: Chrome, Firefox, IE, and Edge.

Ubuntu Server 18.04
nginx 1.14.0
MySQL 10.1.38
PHP 7.2.17 (though I've tried 7.0 as well)

Steps to reproduce:
1.) Open a new ticket (../open.php)
2.) Click on the Insert Image button in Ticket Details
3.) Select an image.
4.) Experience the error.

This also happens when clicking "Choose them" link at the bottom
This also happens when copying/pasting an image into the message body.

The file I usually test with is 8KB, but I've also tried with larger files.
I've also updated the php.ini and changed the settings in the Admin Panel to accept images up to 12MB, but it doesn't seem to actually work as when I do anything over 4MB I get an error (in the browser that the file is too large).

I'm primarily concerned about the customer side of this, as IT will not (typically) be sending any attachments back.

Thanks!

I should not nothing stands out in PHP logs or nginx logs.

Thanks

You are not running a support webserver (nginx) so it could be that.
Since your getting 404 not found errors in the console I would guess that it can't find the files due to a security issue (permissions, firewall, etc).

    ntozier

    I'm not sure it would be a FW issue since it's localhost only.

    Do you know which permissions I might need to check?

    If it were me I would install Apache2 and see if it fixes the problem.
    I do not know enough about nginx to be of much assistance.

    Traditionally whatever the user the Apache server runs as needs permissions to where you are putting the files (the PHP temp folder, and if using attachments on the filesystem the files/folders where the files will reside ). Things that can muck that up are products like SELinux, mod_security, etc.

      ntozier

      I've addressed these issues and am still having problems.
      The website is ran internally, so there's no need for a firewall.
      SELinux is not being used.

      I also installed the "save to filesystem" plugin and created a directory for it, but it did not resolve the issue.

      by "addressed these issues" are you saying that you are not running nginx and installed apache?

      I'll ask the devs to take a look at this thread. But I'm pretty sure that it has something to do with your server configuration or there would be dozens and dozens of people reporting the same issue right now.

      @marshall

      @ntozier is correct in the assumption that this is most likely your server configuration. We run the same version with PHP 7.3 for THOUSANDS of companies and no one has reported this bug. I cannot reproduce this either on any of my local installs of v1.12.

      Try upgrading to PHP 7.3, enable PHP error logging, and retest.

      Cheers.

      Write a Reply...